1. School of EE and Computer Science
Project Initiation
CEN 5016
Software Engineering
© Dr. David A. Workman
School of EE and Computer Science
January 16, 2007

2. Reengineering Process Model
Legacy Test Procedures, Test Data & Results
Legacy
System
Legacy
Baseline
Establish Baseline
Reuse &
Modify Legacy Units
Legacy Requirements
Extract Requirements
Identified
Legacy Units for Reuse & Modification
Proposed
New
Capability
New Requirements
Extract Design
Set of Test-ready Legacy Units
Modified
Requirements
Legacy Design
Re-Test Legacy Units
Requirements
Analysis
Re-test Procedures
See Notes!
Tested Legacy Units
See Notes!
Test Changes
Produce
New Test
Plan
Integration test Procedures
All projects are Reengineering projects. The very first step is to baseline the Legacy system – this means assigning one (perhaps two) people to
Install, compile and run the Legacy (if source code exists ). If test data exists, evaluate Legacy behavior on these data sets. Document problems as these will be topics for discussion with Customer. Baseline activities also include studying Legacy documentation (all team members ) to determine how accurately it describes the Legacy code and behavior – note discrepancies.
Prepare a Baseline Report for discussion with Customer at the earliest possible time. This discussion should focus on differences between the Legacy and Target systems as perceived by Customer and provide the basis for establishing the New Target System Requirements.
Design Changes
Integrate & Test All
Units
New
Design
New Unit test Procedures
Modify & Enhance
Design
Construct & Test new Units
Tested new Units
New
Design
Target
System
January 16, 2007
(c) Dr. David A. Workman

3. Initiation Process Team Member Introduction Schedule Weekly Meetings
Two 2-hour blocks per week dedicated to team meetings. (times and places)
Team communication protocols (e.g. team web site, , etc.)
One meeting should focus on planning activities for the next week(s) and assigning responsibilities to those activities. The other meeting should focus on technical issues. (This is just one approach to structuring your meeting).
Meetings should be spent evaluating solutions, not formulating solutions. When technical problems arise, each person should develop their own solution and justify their approach. Each member circulates their ideas to others through the team lead. Before the meeting scheduled to discuss solutions, each person reviews the approaches of others. The meeting will focus on reaching a consensus solution after all approaches have been evaluated on their merits.
Establish Customer Meeting Schedule
Scheduled Team Meetings may overlap with meetings with Customer
Project Mgr/Customer Availability
At first Team Meeting:
Individual Skills for the given project (work preferences)
Plan baseline activities and responsibilities
Task1: Spin up on Legacy Documentation and Code, plan a meeting with Customer to discuss requirements and answer questions.
Task2: Train team members on development tools and technologies as required.
January 16, 2007
(c) Dr. David A. Workman

4. Deliverables
Report entitled, “Legacy System Baseline Issues and Status”
Identify and describe Legacy artifacts.
Identify and discuss issues and problems in creating a consistent and complete version of the Legacy system.
For each issue/problem describe the method of resolution, current status of resolution, and when resolution should be complete.
Document individual team member responsibilities in the baseline activities.
Report entitled, “Preliminary Requirements for Target System”
Enumerate and describe functional capabilities of the Legacy that carry over unchanged to the Target system.
Enumerate and describe the functional capabilities of the Legacy that will require alteration or enhancement to satisfy Target requirements.
Enumerate and describe functional requirements of the Target system that do not exist in the Legacy or expand its present capabilities.
Assign priorities and significance of all changes and new capabilities.
January 16, 2007
(c) Dr. David A. Workman

5. Team Meetings
Lead prepares and distributes an agenda in advance of the meeting.
Team members should prepare themselves ahead of time for discussing the agenda items.
Lead may assign specific preparation responsibilities to individual team members.
Use meeting time wisely
Arrive on time and finish on time
Discuss solutions to problems that have been prepared in advance; do not solve problems in the meeting, only identify problems that require solutions; problem solving should be an individual activity executed before the meeting begins; in the meeting the problem solver presents and defends his/her solution and the other members present pros and cons. Each solution approach should have equal consideration and the merits should be evaluated. Do not make personal attacks on the presenter.
Lead records and assigns action items and person(s) responsible, and sets a time frame for completing the action items; action items should have concrete deliverable artifacts that other members can evaluate.
Schedule next meeting.
January 16, 2007
(c) Dr. David A. Workman

6. Weekly Process 2a. Evaluate solution alternatives and risks.
2b. Choose an approach for implementation.
1a. Enumerate solution strategies.
1b. Allocate weekly tasks and define deliverables.
3a. Carry out solution plan.
3b. Produce deliverables.
4a. Evaluate deliverables this week.
4b. Set objectives for next week.
January 16, 2007
(c) Dr. David A. Workman

7. Process Phase: Requirements Elicitation
Use Case Modeling
Interview customer and users to gather requirements for new system.
Evaluate Legacy system to determine which target requirements are satisfied and which ones are new.
Formulate, classify and prioritize project tasks around target system requirements (reuse, upgrade, add).
Upgrade Legacy documentation to bring in line with new target requirements.
Review with customer and users
January 16, 2007
(c) Dr. David A. Workman