1 of 11
Homework #2
CMSC 615
(Instructor: Dr. Maccarthy)
Fall 2006
UMBC
8.5/10
Correct AO and fix errors in SEP in HW 5 and you
will receive up to 1.5 more.
Suggest looking at Example SEP I just put in the
references folder.
Project Team Name: iSys
Mollick A. Arefin
Duy Huynh
Book Boss: Mollick A. Arefin
Submission Date: 14 September 2006
CMSC HW #2: Mollick, Bao
2 of 11
1. What is the difference between a Life Cycle Model and and Development Life Cycle
Model? (1pt)
Ans. Life cycle model is collection of all phases and milestones from conception to close
out of the project. It define what work will be performed at each phase, what deliverables
will be produced and when, who is involved at each phase, and how management will
control and approve each work produced in each phase.
The Development Life Cycle on the other hand is a portion of the Life Cycle Model
dealing with the development. This is used as frame work for developing information
systems and software development, because it include requirement, design,
implementation/ coding/ unit testing, integration testing/verification. Unlike the Life
Cycle Model, the development life cycle spend a large portion of the project effort
attempting to clarify the requirements of the project and developing. The Development
Life Cycle Model generally excludes Manufacturing, Deployment, Operations,
Maintenance, and Retirement phases. OK
2. List the activities and milestones associated with the DoD System Development and
Demonstration Phase Life Cycle Model. What kind of model is it? (1pt)
The activities and milestones associated with the DoD System Development and
Demonstration Phase Life Cycle Model are sequentially –
- Milestone: B
“An affordable increment of militarily-useful capability has been
identified”
“The Technology for the increment has been demonstrated in a relevant
environment” (i.e., TRL 6)
“A system can be developed for production within a short time frame
(normally less than 5 years)”
MS B is approval to move forward to SDD Phase
- Refine System Performance Spec & Environmental Constraints
* System Requirements Review (SRR)
- Develop System Functional Specs & System Verification Plan
* System Functional Review (SFR)
- Develop CI Functional (Design to) Specs & CI Verification Plan
* Preliminary Design Review (PDR)
- Develop Product Documentation and Inspection Plan
CMSC HW #2: Mollick, Bao
3 of 11
* Critical Design Review (CDR)
- Design Readiness Review (DRR) Milestone
- Fabricate/Assemble/Code
- CI Verification Development Test & Evaluation (DT&E)
- Verify System Performance: Integrated DT&E & Live Fire Test and Evaluation
(LFT&E)
* Test Readiness Review (TRR)
- Verify System Functionality: System DT&E & LFT&E, & Operational
Assessment (OA)
- Demonstrate System: Combined DT&EO/OT&E/LFT&E
* System Verification Review (SVR)
* Production Readiness Review (PRR)
* Functional Configuration Audit (FCA)
- Milestone: C
“An affordable increment of militarily-useful capability has been
identified”
“The Technology for the increment has been demonstrated in a relevant
environment” (i.e., TRL 6)
“A system can be developed for production within a short time frame
(normally less than 5 years)”
MS C is approval to move forward to Production & Deployment Phase
DoD System Development and Demonstration Phase is a “V” LCM. OK
3. Explain how the “V” model is essentially a classic waterfall model? Why is it drawn
as a “V”? (1pt)
The V model is essentially the classic waterfall model because the sequential nature of
processes; each process must be completed before the next phase can be started. Both the
V model and the classic waterfall model include the requirement, design and analysis,
implementation, testing, and maintenance phases.
The V model is drawn as V shape in order to visually map (or pair up) each design phase
to the corresponding test or verification phase. For example, the Systems Functional
Review (SFR) corresponds to the System verification Review (SVR) . If something does
not fulfill the customer requirement at SVR stage, the “V” model suggests to revisit the
CMSC HW #2: Mollick, Bao
4 of 11
SFR stage directly and make corrections. The bottom of the V represents the Critical
Design Review (CDR) that decides the development; CDR is a very important stage of
the V model. Very Good
4. Go to the DAU Systems Engineering web site
<http://www.acq.osd.mil/ds/se/publications.htm>. Download (and skim) a copy of the
“Systems Engineering Plan (SEP) Preparation Guide”.
5. Download a copy of my recommended SEP Annotated Outline from Blackboard &
read it.
CMSC HW #2: Mollick, Bao
5 of 11
6. 1.Develop an annotated draft Systems Engineering Plan for your Project (IN YOUR
OWN WORDS, DO NOT COPY MINE) (1 pt)
SEP Outline (Draft for HW2)
Title & Coordination Pages
Table of Contents
1. Introduction
1.1. Program Description and Applicable Documents
1.1.1. Program Description
1.1.2. Applicable Documents
1.2. Program Technical Status
1.3. Approach for SEP updates
2. System Engineering Application to Life Cycle Phases
2.1. System Capabilities, Requirements and Design Considerations
2.1.1.
2.1.2.
2.1.3.
2.1.4.
2.1.5.
2.1.6.
2.1.7.
Capabilities to be Achieved
Concept of Operations
Key Performance Parameters
Technical Requirements
Statutory and Regulatory Requirements
Certification Requirements
Design Considerations
2.2. SE Organizational Integration and Technical Authority
2.2.1.
2.2.2.
2.2.3.
2.2.4.
Organization of IPTs
Organizational Responsibilities
Integration of SE into Program IPTs
Technical Staffing and Hiring Plan
2.3. Systems Engineering Process
CMSC HW #2: Mollick, Bao
6 of 11
2.3.1.
2.3.2.
2.3.3.
2.3.4.
Process Selection
Process Improvement
Tools and Resources
Approach for Trades
2.4. Technical Management and Control
2.4.1. Technical Baseline Management and Control (Strategy and Approach)
2.4.2. Technical Review Plan (Strategy and Approach)
2.5. Integration with Program Management Control Efforts
2.5.1.
2.5.2.
2.5.3.
2.5.4.
2.5.5.
Acquisition Strategy
Risk Management
Integrated Master Plan and Integrated Master Schedule
Earned Value Management
Contract Management
This is not an Annotated Outline. It is just an outline (I gave you an example of an AO)
CMSC HW #2: Mollick, Bao
7 of 11
7. Develop drafts for each of the following Sections (5 pts):
1.1.2 Program Description
Amazing Books Inc. has awarded the project of developing a web-based ordering
system to UMBC Corporation [Reference the SOW.]. This web-based ordering
system will allow customers to find and purchase books online using credit cards.
UMBC Management has assigned the task of technically managing the
development of this system to its Systems Engineering Team, the task of
developing the software to the Development Team, and the task of verifying the
product to the Integration and Test Team. The UMBC Management Team will
provide overall project management direction and support services as needed.
[This material really belongs in the Org Structure section, not the program
description.]
[As a matter of style, I would suggest indicating “UMBC Corp is developing a
web-based … using credit cards for Amazing Books Inc..” (who is developing
what for whom). Also indicate why ((e.g., to reduce costs, improve response time,
improve customer satisfaction associated with the ordering and receiving of
books), which should relate to the MOEs (hint, hint).]
The Customer Interface, Inventory, and Shipping capabilities are expected to be
deployed in the next 4 months. Finance capabilities will be deployed within 6
months. Since the time frame for developing Customer Interface, Inventory, and
Shipping capabilities is short (4 months), UMBC Corporation will use the
Concurrent Waterfall approach to enable simultaneous work on multiple stages.
For example, while the Development Team designs the web pages (belongs to the
‘Design’ phase), the Integration and Test Team will negotiate with the online
transaction/security companies (e.g. VeriSign) and the shipping companies like
UPS (belongs to the ‘Implementation’ phase). [Too much irrelevant information.
Also, how will you address the second set of customer desires? It appears they are
looking to get something up and running quickly and then refine it. It does not
appear to be a one-time development activity that can be handled by a single
water fall. Looks like it would require increments, with each increment being a
waterfall.]
This web-based ordering system will be considered as a System of Systems (SoS)
because it will need to subcontract one or more shipping companies e.g. USPS,
UPS, FedEx [No, this is not an SoS project. You are developing a single system to
interact with other systems. In an SoS program you would be developing or
coordinating the development of systems for USPS, UPS, FedEx and all the
banks. In point of fact you are only developing a system for Amazon books to
interact with already existing shipping, banking and publisher systems] Also, it
will require to subcontract a online transaction/security companies (e.g.
CMSC HW #2: Mollick, Bao
8 of 11
VeriSign). These shipping and online transcatin/security companies are standalone systems.
See my write up.
1.2 Program Technical Status (Address DOD Acquisition Life Cycle)
Below are the phases and milestones of the Life Cycle Model that will used for
this program 
Concept Decision










Customer should be able to log on to our web-site.
Customer should be able to find a book of interest.
Customer should be able to add it to their shopping cart.
Customer should be able to purchase items in their shopping cart
using a credit card.
ABI Inventory should order books from the publisher if the
inventory drops below 10 copies of a book.
ABI Shipping should be able to ship a book order (using a shipping
service) to a customer within one working day of the order being
submitted.
ABI Finance should be able to print financial reports showing
income, costs and profit.
ABI Finance should receive payment from the credit card company
within one day.
ABI Finance should pay the publishers and shippers within one
day.
Milestone A
 Consideration of Technology Issues
 Market Research for commercial items, acceptability, standard,
etc.

The Technology Development Phase
(viability of technologies, reduce tech risk, optimal performance, costeffectiveness, etc)
 Operating System Platform: Linux (Red Hat or SUSE; free or
cheap)
 Hardware System (Servers): Linux Networx or Dell or SUN
 Programming Language: Java (J2EE, Servelet, JSP, Beans)
 Web Server: Apache Tomcat or WebSphere.
 Database (RDBMS): MySQL (free or much cheaper than Oracle)
CMSC HW #2: Mollick, Bao
9 of 11

Milestone B
 Completed Capability Development Document (CDD)
 An affordable increment of militarily-useful capability has been
identified
 The Technology for the increment has been demonstrated in a
relevant environment (i.e., TRL 6)
 System can be developed for production within specified deadline

The System Development and Demonstration Phase
The UMBC Development Team will do the followings Complete Subsystem Integration
 Complete Detailed Design
 Complete Demonstration

Milestone C

The Production and Deployment Phase
The UMBC Integration and Test Team will do the followings –
 Integrate and deploy the web-based system to “Achieve an
operational capability that satisfies mission needs”
 Demonstrated process/quality control data

The Operations and Support Phase
UMBC Corporation Management will talk to ABI to come up with the
operations and support (e.g. bug-fixes, upgrade of HW, SW, etc) agreement
later.
You really missed the boat here. Suggest rereading the Chart’s description of
each phase and the purpose of each milestone. Section should include a figure
of the schedule. Also way to much detail about the system. This section is
about the approach used to develop the system. You need to identify the phase
you are in. Suggest you see my write up.
I expect sentences and paragraphs, not bullets
1.3 Approach for SEP Updates
This SEP is upgraded with the following triggers –
CMSC HW #2: Mollick, Bao
10 of 11
Any changes in the LCM, requirements, design, technologies, etc
Milestone A
Milestone B
Milestone C
ADMs
Others
Change Log Table (Most recent update first):
Date
Section
Change Summary
Change Details
09/14/2006
All
Inception of this SEP
Inception of this SEP
I expect sentences and paragraphs, not bullets
2.3.1.1 Technical Development Process (Address Development Life Cycle and
Systems Engineering Process)
2.3.1.2.1 Technical Planning (Include a WBS)
2.4.2 Technical Reviews
CMSC HW #2: Mollick, Bao
11 of 11
8.1 Take the Myers-Briggs Test
8.2 Develop a Team Personality Profile (E/I, S/N, T/F, J/P Result/Score for each team
member)
Mollick A. Arefin: (I, N, T, J) = (33, 75, 25, 44)
Personality type:




moderately expressed introvert
distinctively expressed intuitive personality
moderately expressed thinking personality
moderately expressed judging personality
Duy Huynh (Bao):
(E, N, T, J) = (1, 12, 12, 1)
Personality type:




slightly expressed extrovert
slightly expressed sensing personality
slightly expressed feeling personality
slightly expressed judging personality
Good
8.3 What did you learn?
One thing we have learned is that a Systems Engineering team can (or usually) have
members of diverse personality types. Therefore, the success of the team as a whole
significantly depends on how well the members get along and communicate with each
other. In fact, the diversity in personalities among the team members can well help
developing a better system. The team leaders can utilize the diversified views and
opinions of their subordinates to ensure that all possible scenarios are taken in
consideration in the system design and development.
Good
---------------
CMSC HW #2: Mollick, Bao