DEPARTMENT OF COMPUTER & SOFTWARE ENGINEERING

College of Electrical and Mechanical Engineering (CEME)

National University of Science and Technology (NUST)
PROJECT NARRATIVE

You are required to prepare a design document, based on Unified Process (UP) for
your final year project (FYP). The UP is an iterative process in which the design
documents are refined iteratively. After going through the whole exercise, you will
get a fair idea of the agile iterative development process.
1. Course Information
Course Code and Title: EC-460 Software Design and Testing
Credits: 3 (2+1)
Instructor(s)-in-charge: Dr. Farooque Azam, LE Sundas Ashraf
Course type: Lecture + Lab
Required or Elective: Elective
Course pre-requisites Object-Oriented Programming, Software Engineering
Degree and Semester DCE-40, Semester 8
Month and Year Spring 2022

2. Project Information
Methodology: You must adopt UP Methodology as explained in the lecture with the following diagram: It
shows 4 phases: Inception, Elaboration, Construction & Transition. Moreover, each phase
may have one or more transitions of 1-2 weeks. At the end of each iteration, some artifacts
are required to be delivered
Artifacts: Project Document Containing the following artifacts related to Unified Process (UP): [1].
See link for Templates: http://files.defcon.no/RUP/process/templates.htm .

Do explore the book [1, 2] + internet and other resources to get the guidelines to
appropriately develop the required documents.

Delivery You are required to prepare and submit the artifacts as assignments (1-4) on the due date
Schedule: following the UP methodology. The artifacts will be refined in each iteration; therefore,
you are required to keep a record of each version of the artifact.

See Table 6.1 & Table 6.2 below. The table shows one iteration of the inception
phase and four (4) iterations of the elaboration phase. Each iteration is planned for two
(2) weeks.
 The tables also explain, how artifacts are refined in each iteration. Any missing
information can be acquired from the book [1]

Hence you will submit each project deliverable of two (2) weeks. The last deliverable
will be a highly refined document.

You will also be required to present your project document in the last class.
Deliverables  4 Assignments
 5th deliverable will be wholesome and fully refined and presentable version and
will be considered as Project Report
 Project Presentation

Artifacts Incep. Elab.1 Elab.2 Elab.3 Elab.4

Deliverables (fortnightly)  A1 A2 A3 A4 PR
1. Vision and Business
start refine refine refine finalize
Case
2. Use-Case Model start refine refine refine finalize
3. Supplementary
start refine refine refine finalize
Specification
4. Glossary start refine refine refine finalize
5. Risk List & Risk
start refine refine refine finalize
Management Plan
6. Prototypes and proof-
start refine refine refine finalize
of-concepts
7. Iteration Plan start refine refine refine finalize
8. Phase Plan & Software
start refine refine refine finalize
Development Plan
9. Development Case start refine refine refine finalize
10. Domain Model start refine refine finalize
11. Design Model start refine refine finalize
12. Software Architecture
Document start refine refine finalize
13. Data Model start refine refine finalize
14. Use-Case Storyboards,
UI Prototypes start refine refine finalize

Homework: 4 Assignments
Project reports: 1 Design project based on Lab
Quizzes: 5 Quizzes
Grading: Theory 66%
Quizzes: 10%
4 Assignments: 10%
OHTs: 30%
Final Exam: 50%
Labs 34%
Lab Tasks 40%
Lab Mid 40%
Project Presentation 10%
Final Project Report 10%
Reference Material
Reference: [1] Applying UML and Patterns: An introduction to OOA&D and
the Unified Process, by Craig Larman, 3rd Edition
[2] See link for Templates:
http://files.defcon.no/RUP/process/templates.htm

Table 6.1. Sample requirements effort across the early iterations; this is not a recipe.

Discipline Artifact Comments and Level of Requirements Effort (10 weeks Plan)
Incep Elab 1 Elab 2 Elab 3 Elab 4

2 week 2 weeks 2 weeks 2 weeks 2 weeks

Requirements Use-Case 2-day Near the end of Near the end of Repeat, Repeat with
Model requirements this iteration, this iteration, complete the goal of 80-
workshop. Most host a 2-day host a 2-day 70% of 90% of the
use cases requirements requirements all use use cases
identified by workshop. workshop. cases in clarified and
name, and Obtain insight Obtain insight detail. written in
summarized in a and feedback and feedback detail.
short paragraph. from the from the
implementation implementation Only a small
Pick 10% from work, then work, then portion of
the high-level list complete 30% complete 50% these have
to analyze and of the use cases of the use cases been built in
write in detail. in detail. in detail. elaboration;
This 10% will be the remainder
the most are done in
architecturally construction.
important, risky,
and high-business
value.
Design Design none Design for a repeat repeat Repeat. The
Model small set of high-risk and
high-risk architecturally
architecturally significant
significant aspects should
requirements. now be
stabilized.
Implementation Implementa none Implement Repeat. 5% of Repeat. Repeat. 15%
tion Model these. the final system 10% of of the final
(code, etc.) is built. the final system is
system is built.
built.
Project SW Very vague The estimate a little better… a little Overall
Management Developme estimate of total starts to take better… project
nt Plan effort. shape. duration,
major
milestones,
effort, and
cost estimates
can now be
rationally
committed to.
 Table 6.2. Sample UP artifacts and timing. s - start; r – refine

(Provided for getting the Idea)

Discipline Artifact Incep. Elab. Const. Trans.

I1 E1..En C1..Cn T1..T2
Iteration
Business Modeling 1. Domain Model s r
Requirements 2. Use-Case Model s r
3. Vision & Business Case s r
4. Supplementary Specification s r
5. Glossary s r
6. Use case Story Boarding, UI s r
Prototypes
Design 7. Design Model s r
8. SW Architecture Document s r
Project Management 9. Risk List and Risk Management s r
10. Prototyping and Proof of s r
Concepts
11. Phased Software Development s r
Plan
12. Development Case s r
13. Iteration Plan s r