Successful Projects

Thaddeus ‘Ted’ NOGA
Successful Projects

Successful Projects
08-Oct-2015 02:20 Z:tempw indows20151008022044_e585b04e71d053a95ca0ed4d1e3c98
b47f75d13a1430fe62-a560-42ae-955a-59d8d69d692d-151008022157-
lva1-app6891.docx
Page 2 of 18
Project List.............................................................................................................................3
Introduction............................................................................................................................7
1. Experience .....................................................................................................................7
2. Breadth of Knowledge .....................................................................................................7
3. WCB Practices and Standards.........................................................................................7
4. Models and Patterns .......................................................................................................8
5. Iterative Report Development ..........................................................................................9
Projects ................................................................................................................................11
6. Y2K at Hydro ................................................................................................................11
6.1. Telon 2.0c to 2.1b to 2.3 to 2.4 ..................................................................................11
6.2. CICS 2.1.2 to CICS 3.3 to CICS/ESA 4.1 ...................................................................11
6.3. COBOL/VS to COBOL II to COBOL MVS ...................................................................11
6.4. PL/I 1.5.1 to PL/I 2.3.0 ..............................................................................................11
6.5. ISPF 3.5 to ISPF 4 ....................................................................................................11
6.6. IBM’s Language Environment (known as LE)..............................................................11
6.7. various CICS software:..............................................................................................11
6.8. Duration: Spring, 1995 to Fall, 1997 ..........................................................................11
6.9. Goal: Seamless upgrades without disrupting existing development environment ..........11
6.10. Plan: ........................................................................................................................11
7. Change Management....................................................................................................11
8. SQL Server Upgrade ....................................................................................................12
Career Experience .............................................................................................................14
9. Systems Analyst...........................................................................................................14
9.1. Workers Compensation Board of Manitoba 1999 to present ........................................14
10. Systems Engineer/Technical Architect .......................................................................14
10.1. SHL/Systemhouse 1998-1999 ...................................................................................14
10.2. MTS.........................................................................................................................14
11. Support Specialist I...................................................................................................14
11.1. Manitoba Hydro 1992-1998 .......................................................................................14
11.2. Duties: .....................................................................................................................14
12. Employee Information Programmer Analyst III ............................................................15
12.1. Manitoba Hydro 1991-1992 .......................................................................................15
13. Application Programmer Analyst III ............................................................................15
13.1. Manitoba Hydro 1989-1991 .......................................................................................15
14. Application Programmer Analyst II .............................................................................15
14.1. Manitoba Hydro 1987-1989 .......................................................................................15
15. Computer Programmer..............................................................................................16
15.1. St. Boniface General Hospital Vascular Laboratory 1985-1989 ....................................16
Education.............................................................................................................................17
16. In-House Training .....................................................................................................17
17. University of Waterloo (Partial) ..................................................................................17
18. University of Manitoba...............................................................................................17
19. Brandon University ...................................................................................................17
20. University of Winnipeg ..............................................................................................17
21. Red River Community College ...................................................................................17
Strengths .............................................................................................................................18
22. WCB Performance Appraisals ...................................................................................18

Successful Projects
08-Oct-2015 02:20 Z:tempw indow s20151008022044_e585b04e71d053a95ca0ed4d1e3c98b47f75d13a1430fe62-a560-42ae-955a-
59d8d69d692d-151008022157-lva1-app6891.docx
Page 3 of 18
Project List
Project Name Responsibilities/Role Length of
Project
1 SQL Server Upgrade 2005 and 2008
Lead developer.
Many Delphi apps needed upgrading.
Inconsistentdevelopmentrequired unique solutions to fix manyproblems.
Solutions followed Java developmentstandards.
2007 & 2010
2 TIDAL Upgrade Developed testplan based on user requirement.
Lead developer.
2009
3 Manitoba HUB Integrated WCB and Manitoba HUB
Lead developer to design and implementsolution.
Solution leveraged existing Emerge Task Engine code. New messages can now simplybe added
by creating new message processors.
First WCB application to connectusing MQ Series with an external client.
Technologies used: MQ Series,Castor Custom XML Mapping,WCB Framework
2008
4 External Projects Lead developer and designer.
Clearances IVR – worked with MTS staff.
- Received IVR Clearance requests from MTS and updated Clearance Requests in the WCB
Database.
- Created WCB firm list(with Clearance Statuses) to be used to update the MTS IVR
database.
- These updates run dailyusing various technologies: TIDAL, FTP, Java
Manitoba Health Data Sharing – worked with the DepartmentofHealth on data exchange
- Created application to send and receive data between WCB and Manitoba Health.
- Worked with Manitoba Health to come up with a data exchange process
Canada Pension Plan
- Redeveloped the Emerge Canada Pension Plan Data Exchange
- Worked closelywith CPP Payments of Service Canada
2002
2006
2010

Successful Projects
59d8d69d692d-151008022157-lva1-app6891.docx
Page 4 of 18
Project
5 RetirementAnnuity Implementation Design;move the conceptual design to implementation design.
Develop reports to assess impact.
Design and implementpermanentsolution.
2011
6 Injury CostReport Lead Developer
Model and analyze problem.
Redesign report with a detail report.
2010-11
7 Case ManagementReports Lead Developer
Redesign reportwith a detail report.
2007
8 Pension ReportBalancing Lead Developer
2010
9 Canada Pension Plan Reports Lead Developer
Review problem.
2010
10 Firm Experience Reports Lead developer and designer
As proof of concept, first jobs to be migrated from the Mainframe to Emerge.
Resigned the Firm Experience and associated costreports;the statements and reports were on the
same data.
Operational Impact: The firm experience statements and reports no longer needed to be balanced
by operations and Finance resulting in a very shortbatch window in the evening.
2004
11 T5007 Automation Lead developer.
Created a new standard for creation of skeletons for submission ofjobs on the mainframe.
This was implemented with the automation ofT5007s.
Incorporated design changes to save time for development,testing and production submission of
jobs.
Model and design allowed developmentto be started December 29th
and completed by December
31st
in time for T5007 processing in the new year.
2002

Successful Projects
59d8d69d692d-151008022157-lva1-app6891.docx
Page 5 of 18
Project
12 LMI Assistantdeveloper.
Responsible for creating a new batch componentfor LMI to capture data from an HRDC web site
and update the LMI databases with the information.
This was the firstbatch Java application developed bythe WCB.
2002
13 Web Security Administration Ted developed the batch components ofthe web Security Administration application.
This was the second ofthe batch Java applications developed bythe WCB and was a part of the
system deployed for online accidentreporting.
2002
14 Clearances Developed the batch components ofthe Clearances application.
Developed some ofthe components for Clearances reporting.
This project also included the setup ofFTP between the WCB and MTS on the Java platform.
2002
15 EJES Transitioned WCB from Flasher to EJES.
This involved training of application development,end user support,and operations staff.
2002
16 Sys*Admiral Prime administrator for sys*Admiral.
Assisted in resolving manyof the issues thathave arisen with the product.
As the new version of the software is implemented,transferred administrator responsibilities to the
Technical Services staff.
2002
17 ESP Implementation Created process to adoptESP as a mainframe job scheduling system.
Developed procedures for creating and submitting jobs. Use ofESP is still limited atthis time but
will increase as new mainframe jobs are added.
2002
18 CICS Shutdown Implemented a process to automate the CICS shutdown and startup.
This helps streamlined processes for Operations.
2003
19 Emerge Project Worked on the following:
- The user interface for the Reference Master (Java); developed HTML prototype to show
functionality
- Various CICS changes
- Create forms (Crystal Reports);Mainframe report migration
- Notes in Emerge (Java); developed implementation based on prototype
2003

Successful Projects
59d8d69d692d-151008022157-lva1-app6891.docx
Page 6 of 18
Project
20 Mainframe Printer
Replacement
Mainframe printer project: modify mainframe COBOL programs thatused AFP (Advanced Function
Printing) technologybecause the XEROX printers did notsupportAFP.
Modified the COBOL programs to create files that could be downloaded,from the mainframe,and
used in Crystal Reports.
This projectwas particularlyurgent to ensure no disruption in creating WCB claimants’ cheques.
The current IBM printers had been off of warranty for some time and there was a worry that cheque
printing may be unavailable.
2003
21 Manitoba HUB Design and develop application to receive business registration information to the Manitoba HUB.
Manitoba HUB was incorporated in its entirety to Optimal.
2008-2009
Many more Service Requests

Successful Projects
08-Oct-2015 02:20 Z:tempw indows20151008022044_e585b04e71d053a95ca0ed4d1e3c98b
47f75d13a1430fe62-a560-42ae-955a-59d8d69d692d-151008022157-lva1-
app6891.docx
Page 7 of 18
Introduction
1. Experience
Twelve years prior to coming to WCB, I have worked as a lead programmer and technical architect at 3
major organizations. I believe this experience will be invaluable to me as an Application Solution
Architect. Planning and modeling were instrumental in the successful implementations of many projects,
culminating in a successful implementation of all Y2K changes in 1997. This project was key when I was
hired at WCB to assist in Y2K changes at WCB. Up to WCB moving from the Mainframe, many design
models were implemented to improve efficiency, especially in Operations.
I am a proponent of simple practices and standards in development. This document is an example of a
Word template. This template has been used to report on projects that I have worked on. The template
has allowed me to create documents quickly with the same look and feel. I also use Excel templates
extensively to report test output. I am able to quickly produce a professional look looking report from a
spreadsheet without doing the repetitive work of updating page layout. I am now able to concentrate on
the data knowing that the spreadsheet will have a consistent look and feel. Particular standards have
been developed for WCB’s Java Web development but I have applied the same standards where
appropriate in all my development activities.
2. Breadth of Knowledge
My experience at WCB Spans the following 3 environments:
1. The Mainframe; my role was corporate technical expert,
2. Developing and maintaining Delphi applications, and
3. Java Web development.
With the above experience, I am able to work on any project assigned to I/T.
In the Business As Usual (BAU) Team, junior and senior developers come to me for advice on how
applications work. I stress how each application relates to another. No application can be worked on in
isolation without causing unforeseen side-effects in another application. A group of applications must be
worked on as whole, searching for side-effects. As an example, the following applications should be
tested together to see how the changes affect each application:
1. Web Security
2. Delphi Client Server Security
3. Claims Intake System (CIS)
4. Employer Incident Reporting
5. Print App
The above applications needed to be tested to ensure a data validation request in both CIS and Employer
Incident Reporting did not adversely affect Print App. The security applications are tested alongside to
familiarize the developer with security.
3. WCB Practices and Standards
WCB follows a basic set of practices and standards throughout the development and maintenance of all
applications.
Each developer at WCB has received training in the Rational Unified Process (RUP); further known as
RUP Lite.
The following is a list of broad phases used at WCB that overlie all development activities at WCB:

Successful Projects
app6891.docx
Page 8 of 18
1. Inception
2. Elaboration
3. Construction
4. Transition
The above broad phases involve the following activities:
1. Modeling
2. Requirements
3. Analysis and Design
4. Implementation
5. Testing
6. Deployment
Modeling that happens during the Construction Phase shows the iterative nature of the development
activities during the RUP Lite process. Rather than having a complete solution at each phase, a partial
solution is acceptable. These partial solutions led to an iterative approach to development where, at each
phase, there is a partial working application that clients can review. These reviews will show any
shortcomings in development at the earliest stage. On the other hand, these reviews will show any
missing requirements that may have been missed. The iterative development process also involves
clients at all stages helping ensure that the final product is as close as possible to what is needed.
4. Models and Patterns
I, myself, apply this process intuitively in all my activities. Whether I’m building a Crystal Report, TIDAL
job, Emerge functionality, or a database stored procedure, I follow the same methodology. As an
example, rarely is a solution known from the beginning. I begin with small building blocks and create
something that is working. As I learn more about a problem, more functionality is added. This process is
followed until a solution is complete; by complete, I mean acceptable to the client.
In Java development, there is a Model/View/Control Pattern. WCB developed its own Web Development
Framework. With the framework, a lot of technical details are eliminated from development. Developers
simply ‘plug in’ code into the framework. The framework leverages code by reuse. I like the framework
because the framework allows me to work on any application and I can find the code quickly and make
any changes and/or additions that are needed. Any developer can now work on any application that uses
the WCB Framework.
Also, developers need not recreate models in their entirety. The WCB framework has a set of models
that show how the framework interacts with system components. The WCB typically uses the following
models:
1. Class Models
2. Sequence Diagrams
3. State Diagrams
Models can take many forms. During 1 of my last projects, I developed a high level diagram of how data
from Emerge flows to reports. With this diagram, I was able to show a number of solutions and show
which solution would be the best and why a chosen solution was implemented.

Successful Projects
app6891.docx
Page 9 of 18
5. Iterative Report Development
I also create a series of spreadsheets which show partial solutions driving to the final solution. This
particular technique was used to solve problems with the following reports (SR Projects):
1. Case Management Performance Reports
2. Canada Pension Plan Reports
3. Pension Reports
4. Expansion of Coverage
As a result of the iterative nature of the solution, I was able to show to the clients how the reports are
created. From the iterative reports, problems were found in the report requirements; the report
requirements were corrected and the reports are produced today without any problems. As a side effect,
clients now use detail reports to support the summary reports. The detail reports are useful to clients
themselves to identify any problems that show up in the future. Future problems may occur but now the
clients have the tools to make decisions themselves without the involvement if I/T.
The following Excel spreadsheet shows the detail from which a summary report was created in Service
Request NR66294. Once the detail was reviewed, further requirements were added which led to the
successful completion of the report. The client has a detail report supporting the summary report. Since
implementation 4 years ago, I/T has not received any requests asking for explanation of totals on the
summary report.

Successful Projects
app6891.docx
Page 10 of 18
Note: The detail is shown; from the detail, secondary reports were developed (shown as tabbed
worksheets). From the secondary reports, the final summary report was produced. Three major
steps were needed to produce the final report.
Since developing this standard, many reports have been created quickly and correctly; clients are able to
see intermediate results and address problems quickly. The following are major efforts to find out how
reports produce their numbers:
1. NR149236
2. NR146153
3. NR125024
4. NR96207
At present, I am not able to show the data model that I created for Emerge Reference Maintenance. The
models have been incorporated into the IBM Rational Software Architect; I have not been shown how to
access the models. I created the Reference Maintenance Model using Rational Rose.

Successful Projects
app6891.docx
Page 11 of 18
Projects
6. Y2K at Hydro
6.1. Telon 2.0c to 2.1b to 2.3 to 2.4
6.2. CICS 2.1.2 to CICS 3.3 to CICS/ESA 4.1
6.3. COBOL/VS to COBOL II to COBOL MVS
6.4. PL/I 1.5.1 to PL/I 2.3.0
6.5. ISPF 3.5 to ISPF 4
6.6. IBM’s Language Environment (known as LE)
6.7. Various CICS software:
- Superoptimizer 2.5.24
- CA-INTERTEST 4.1 to 4.4 to 5.3 to 5.4
- CA-SYMDUMP 4.1 to 4.4 to 5.3 to 5.4
- CSP 3.2 to 3.3)
6.8. Duration: Spring, 1995 to Fall, 1997
6.9. Goal: Seamless upgrades without disrupting existing development environment
6.10. Plan:
a. Requirements:
- Determined changes needed for Y2K compliance
- Determined present software inventory being used
- Determined state of current in-house applications
b. With the requirements in place, the plan was completed by overlaying the IBM migration
path.
- The plan now was broken into 5 6-month segments with any changes being made at the
beginning of a 6-month period and monitored.
- Once the system was stable, another change would be made.
- With this timeline, changes could be tested and moved to production without disruption of
any development.
7. Change Management
Modelled, designed and implemented a change managements system at Hydro. Initially, the change
management performed and logged simple change. Over time, many other I/T system artefacts were
added. Eventually, the system was capable of updating whole systems, particularly during Y2K
implementations.
The change management system allowed many developers to work on the same project and have all
the changes moved from development to production at the same time. The developers were not just
application programmers but included changes made by infrastructure specialists and database
administrators.
As a final note, the change management system kept track of all approvals allowing moves from
development to certification to production. Today, proof of approval is needed by auditors.

Successful Projects
app6891.docx
Page 12 of 18
In particular, this project demonstrated the power of incremental development. Slowly from 1987 to
1994, the change management grew in capability but maintained its simplicity. Functionality could be
added, changed and removed as needed without affecting whole.
8. SQL Server Upgrade
The project included 2 major sub-projects:
1. SQL Server Upgrade
2. Application updates
SQL Server Upgrade involved testing of the following technical infrastructure:
1. WebSphere Data Sources: Emerge, TIDAL
2. TIDAL: ODBC connections
3. Crystal Reports
4. Crystal Enterprise
Applications updates were done separately because of the number of changes needed. All Delphi
applications needed BDE converted to Microsoft’s ADO. The change itself was straightforward but
other problems were exposed that needed to be corrected in order for the applications to work.
Difficulties arose as applications were inconsistently developed. Each application used different
techniques us similar technologies which required unique solutions. Each solution was documented
in a project document for future reference.
The conversion of the applications began with a proof of concept. A small, simple application was
converted and upgraded successfully. From this point, applications were changed from simple to
more complex in order to gain confidence in the solution. In the end, all applications except Claims
Intake System (CIS), ESIS and Financial Implication Reporting (FIR) were changed.
The following is a list of applications that need to be updated to Microsoft’s ADO:
1. Annuities
2. Appeal Commission
3. Batch Driver
4. Delphi Security Admin
5. Fair Practice
6. Health Care Provider
7. Inbound Document Generator
8. Medical Review Panel
9. Occupational Disease Unit
10. Outbound Document Generator
11. QA Stats
12. Review Office
13. Risk Management
Several other applications were tested with SQL Server Upgrade but did not need any changes.

Successful Projects
app6891.docx
Page 13 of 18
Developed test plan which included WCB-written applications and run-time environments, such as
TIDAL and Crystal Enterprise. The test plan also needed to make sure any queries to SQL Server
still worked as they did before.
Began the project by choosing a simple application, Risk Management, as a proof of concept that
Delphi’s BDE can be converted to Microsoft’s ADO.

Successful Projects
app6891.docx
Page 14 of 18
Career Experience
9. Systems Analyst
9.1. Workers Compensation Board of Manitoba 1999 to present
10. Systems Engineer/Technical Architect
10.1. SHL/Systemhouse 1998-1999
a. Great West Life
- Team Leader
- Design update cheque printing application
- Telon-based application; Telon is a development framework used on IBM Mainframe,
similar to WCB Web Framework.
10.2. MTS
b. Team Leader
c. Work Force Management System (WFMS)
- Design proof of concept
- Implement design using IBM Mainframe CICS and MQ Series
- Integrate existing Service Order System (SOD)
- Assist UNIX and NT teams with MQ Implementations
11. Support Specialist I
11.1. Manitoba Hydro 1992-1998
Assistant Support Specialist at Manitoba Hydro. Duties include supporting the complete
mainframe application development environment (See Skills), change control/configuration
management (developed in-house application to manage production environments) and
support for Intranet development. Provided debugging, problem resolution and evaluation of
new products.
Under the general direction of the Supervisor, Systems and Data Management, or other senior
Support Specialists, will be the support specialist responsible for the technical support and
maintenance of the Corporation’s CICS, change control and Intranet application development
environments. Provide technical expertise in the in areas of: IBM mainframe software,
especially CICS; development tools and programming languages; system performance and
availability; and research and development on new system software and techniques for a more
cost-effective use of computers within the Corporation.
11.2. Duties:
- Responsible for the support, maintenance and implementation of system and application
changes of the Corporation’s CICS production and development environments, ensuring
that it is maintained at maximum availability and optimum performance, and continuously
monitored and improved or expanded as required.
- Responsible for the administration and support of the Corporation’s Intranet application
development environment.
- Responsible for change control in the IBM computing environment, including the support
and development of enhancements to the change control software.

Successful Projects
app6891.docx
Page 15 of 18
- Provide consultative expertise to the Corporation’s Information Technology staff in regards
to efficient programming techniques, system design, problem resolution in CICS, TSO/ISPF
and batch environments, and the Windows NT environment.
- May act as project leader for assigned projects.
- Gather and tabulate computer system operating statistics for use in determining the
efficiency and reliability of the CICS systems and to ensure performance objectives are
being met.
- Perform diagnosis and correction of development and production problems in both batch
and CICS online environments.
- Participate in the development of specialized applications such as utility, monitoring, and
analysis programs.
- Participate in the planning and execute the tasks associated with the evaluation, installation
and maintenance of mainframe computer software and hardware products.
- Perform research and development on new system software and techniques.
- Participate in the diagnosis of the cause of a system software failure and take appropriate
remedial action, assuring that the system software is available as soon as possible after the
failure, and ensuring availability objectives are being met.
- Participate in implementing strategies to improve efficiency and reliability of CICS system
and application software.
- Act as an instructor, advisor, or tutor in the presentation of in-house education.
- Monitor the activities of, and maintain a close liaison with, vendors providing computer
hardware, software, and services.
- Evaluate the impact of any changes in vendor offerings, and participate in devising and
implementing strategies to incorporate changed offerings.
- Initiate and monitor problem solving activities undertaken by vendors providing computer
hardware, software, and service. Coordinate the flow of information between the vendor
and Manitoba Hydro.
- Maintain a state-of-the-art knowledge of computer hardware, software, and services.
- Other related duties as assigned.
12. Employee Information Programmer Analyst III
Payroll/Personnel System development and maintenance. On-call support. Development new
features/extensions: new reports, interfaces to existing systems.
13. Application Programmer Analyst III
Fulfilling the role of senior programmer analyst for the Financial systems and responsibilities it
entails. Ensuring smooth operation of the production system (including on-call support).
Analysis and specification of new work, delegation of work, primary contact with end users.
14. Application Programmer Analyst II
Financial systems development and maintenance.

Successful Projects
app6891.docx
Page 16 of 18
Provided transition support from old to new Meter Record System; developed complete batch
reporting system for Meter Records System (Y2K compliant).
On-call support. Improved existing procedures for system reliability.
Assisted in the development of Hydro’s change control/configuration management system.
15. Computer Programmer
15.1. St. Boniface General Hospital Vascular Laboratory 1985-1989
Redeveloped batch data entry of Vascular Laboratory Patient Tests.
Developed new SPSS application into a data warehouse. The lab was now able to see the
number of tests being performed as well as patient recovery.
STANDARDS: this project taught me to follow standards and best practices. Short cuts only
work in the short term.
The data entry redevelopment and development of a new SPSS application was caused by the
lack of standards. The standard that was not followed was SPSS itself; the application failed to
migrate from version 1.9 to 2.0 because of syntactical reasons.
The new application incorporated the batch data entry. Simply storing the SPSS database in
tab-delimited format allowed quick and easy updates by the batch data entry. Performance
improved by 90% thus reducing costs paid by the lab for computing costs.
As a result of the savings in computing costs, a PC was purchased and the lab data and
application were moved to SPSS/PC.

Successful Projects
app6891.docx
Page 17 of 18
Education
I am always learning, either through formal training offered at WCB or through continuous learning on my
own time. At home, I have amassed a library of books ranging from Java, Web programming, security,
operating systems, Office products, to name a few. Whenever I find my training missing, I will first see if
WCB offers training or begin self-training by searching and finding books that I can read. I always look
forward to my job and finding new and better ways of doing my job.
16. In-House Training
I have completed many in-house training; training offered by both I/T and H/R.
Please see my personnel file for a complete list of training and courses that I have taken.
17. University of Waterloo (Partial)
Studied Abstract Data Type; precursor to today’s Object Oriented Programming.
18. University of Manitoba
Bachelor of Computer Science, Honors with 1st
19. Brandon University
Studied Computer Science and Financial Accounting.
20. University of Winnipeg
Completed the Certificate Program in Administrative Management June 1st, 1994.
The following is a list of courses in the program:
- Effective Oral Communication
- Effective Written Communication
- Essentials of Management
- Financial Management
- Systems Analysis and Decision Making
- Human Dynamics in Organizations
- Organizations and Change
- Introduction to Micro Computers
- Word Processing using WordPerfect 5.1
- Stress Management
- Training and Development
21. Red River Community College
Completed the following courses:
- Computer Networking
- PowerBuilder Introduction
- PowerBuilder 2

Successful Projects
app6891.docx
Page 18 of 18
Strengths
22. WCB Performance Appraisals
Ted is an excellent team player, he’ll do whatever it takes to assist in team success. Ted’s ability to
work in all of our environments continues to provide a strength to the department in the ability to
leverage his expertise in these environments based on where the workload is greatest or in most
need.
The quality of Ted’s work is very good. He always puts in extra effort to ensure that his code is correct
and has comprehensive error handling. He has come a long way in adapting himself to the new J2EE
environment.
Ted’s written communication is clear and well organized. He makes good use of space and presents
his information simply and effectively. His oral communication is not always succinct but is getting
better
Ted has two main strengths: an excellent work ethic combined with dedication to the job, and his
willingness to help others.
Ted will spend enough time on a project to produce a high-quality result. He has attacked the J2EE
environment with the same intensity and dedication, and is learning rapidly. Ted will “submerge”
himself in the technical environment with the goal of developing a thorough understanding.
Ted can be counted on to put in extra effort, when required, to resolve problems or complete
assignments.
I was sent the following to a question for my 2003 P & DS; I believe that I’ve lived up to the ideal of a
Systems Analyst (SA) which leads to the Application Solution Architect:
In order to be an effective SA in my department, Ted, you need to know the tools we use. My
"dream SA" can use Java, Delphi, CICS, Crystal Reports, and write effective SQL. And, that's
just the programming aspect of the job. An SA must have analysis/design tools in their toolbox as
well: data modeling, UI modeling, process modeling, use cases, Rational Unified Process, and so
on. This stuff, by the way, is what a REAL SA does! That's why it shows up first under the Job
Duties section of the job description.

Successful Projects

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (13)

Similar to Successful Projects

Similar to Successful Projects (20)

Successful Projects