HIGHER COLLEGES OF TECHNOLOGY

Computer and Information Science

Project

Course CIS2303- Systems Analysis and Design

Assessment Method Group Project

Date of Assessment Week 13 Deadline(s)

Maximum Mark 100 Percentage of Final Grade 25%

 The entire project/case study/poster is designed and developed by me (and my team members).
 The proper citation has been used when I (and my team members) used other sources.
 No part of this project has been designed, developed or written for me (and my team members) by a third party.
 I have a copy of this project in case the submitted copy is lost or damaged.
 None of the music/graphics/animation/video/images used in this project have violated the Copy Right/Patent/Intellectual Property
rights of an individual, company or an Institution.
 I have the written permission from people who are featuring in this project.

Date: / /

Student HCT ID Student Name Signature

For Examiner’s Use Only:

CLOs CLO1 CLO2 CLO3 CLO4 Oral Defense Total

Marks Allocated 4 22 12 12 50 100

Marks Obtained

CIS2303-Project Description P a g e 1|
 PROJECT OBJECTIVES

This course is a project intensive course. It allows students to have an experience with the project analysis and design. The
students should describe their project. They must determine, gather and interpret the requirements to define a project
specification, to analyze and design it. The main objectives of this project are:

 Understand the business requirements and analyze them;

 Identify and interact with stakeholders to ensure that their needs are being met;
 Define an analysis model using different UML diagrams and follow an appropriate development process;
 Define a high-level design model. The design should be traceable to the analysis model;
 Respect the different phases of the chosen development process.

PROJECT DESCRIPTION

Choose one of the case studies from the following:

1- Alumni Management System

2- Capstone Project Management System
3- Hotel Information Management System
4- Legal Courts Management System
5- Online Food Ordering and Delivery System
6- DHA COVID Response System
7- Project Management Information System
8- Warranty Management System
9- Distance Learning System

Description of the case studies is presented in the attached files.

Consider the requirements for your chosen case study. The requirements are intentionally incomplete and redundant. Your
mission is to:

1. Initiate the project (Q1, Q2);

2. Define, discover, review, document, and understand the user's needs and constraints for the system by using the
requirement engineering techniques (Q3, Q4, Q5, Q6);
3. Analyze and specify the requirements (Q7, Q8, Q9, Q10);
4. Design the software architecture (Q11, Q12).

QUESTIONS
Use STARUML to answer the questions from 4 to 12. Document each question by screenshots of diagrams and/or product
backlogs.
1. Which methodology would you like to adopt for this project? Justify your choice by listing 2 arguments.
2. Conduct the feasibility study for this project.
3. Define, discover, review, document, and understand the user's needs and constraints of the to-be system using at least
two requirements gathering techniques. Justify your choice.
4. Create an activity diagram describing the behavior of the business process.
5. What is the perimeter of the to-be system?
6. Identify the functional and non-functional requirements of the to-be system?
7. According to your answer in Question 1 and 6, describe the requirements using either a product backlog or a use case
diagram.
8. For each sprint/iteration, create a system sequence diagram describing the behavior of or a user story/a use case.
9. For each sprint/iteration, create a fragment of the domain class diagram describing the structure of the to-be system.
10. Merge/Refine all fragments to define the domain class diagram.
11. Which architectural style you like to adopt to design the to-be system?
12. Create a high-level architectural model of the to-be system.

CIS2303-Project Description P a g e 2|
 REPORT AND PRESENTRATION STRUCTURE

REPORT 50%
The Project is done by a group called ProjectTeam that contains at most 4 members. Any help you receive from classmates
should be limited and should never involve details of how to model a solution. You must abide by the following: You may not
work as a partner with another ProjectTeam. The project team needs to submit just one hard copy of the report with the above
cover page. You need to use the Discussions Link in BBL to record the collaboration between all ProjectTeam members The
following is a list of what is expected for deliverables. Feel free to add any sections that you want.

CLO Aim Deliverable Content

 Cover page
The focus is to evaluate  Table of Content
the overall structure and  Table of Figures
language efficacy of the  Introduction
report.  Answers of all questions
 Conclusion listing the individual student reflections
 References
CLO1: Compare  Provide answer to question 1:
The focus is to evaluate 1. Which methodology would you like to adopt for this project?
a range of
the choice of System
system Justify your choice by listing 2 arguments.
Development
development
methodology.
methodologies
 Provide answers for questions 2 to 8:
Specification –An 2. Conduct the feasibility study for this project.
explanation of the 3. Define, discover, review, document, and understand the
problem to be solved in user's needs and constraints of the to-be system using at
terms of business least two requirements gathering techniques. Justify your
process. choice.
CLO2: Create Requirements Analysis 4. Create an activity diagram describing the behavior of the
behavioral business process.
and Definition is the first
models to 5. What is the perimeter of the to-be system?
document stage in the systems 6. Identify the functional and non-functional requirements of
system analysis and design. This the to-be system?
requirements stage breaks down 7. According to your answer in Question 1 and 6, describe the
functional and non- requirements using either a product backlog or a use case
functional requirements diagram.
8. For each sprint/iteration, create a system sequence diagram
to a basic design view, to
describing the behavior of or a user story/a use case.
provide a clear system
development process
framework. The focus is
to describe the
behavioral models.
CLO3: Create Requirements Analysis  Provide answers for questions 9 and 10:
structural and Definition. The focus 9. For each sprint/iteration, create a fragment of the domain
models to is to describe the class diagram describing the structure of the to-be system.
specify system structural models. 10. Merge/Refine all fragments to define the domain class
requirements diagram.
CLO4: Create a The focus is to evaluate  Provide answers for questions 11 and 12:
high-level the transition to design 11. Which architectural pattern you like to adopt to design the
software model. to-be system?
architectural 12. Create a high-level architectural model of the to-be system.
design model

INDIVIDUAL PRESENTATION, COLLABORATION, AND FOLLOW-UP QUESTIONS 50%

CIS2303-Project Description P a g e 3|
 You will give a 25-minutes class presentation of your work and answer all interview questions (Please check the below rubric).
The presentation should include all report items. One general comment is to add more figures/diagrams of your system to help
with your explanation of your project (A picture is worth a thousand words). In addition, the student ability to collaborate and
participate in the deliverable accomplishment will be assessed. Students should keep track and record the collaboration
between team members by using BBL Discussion Board.

PROJECT DELIVERABLES AND GRADES DISTRIBUTION

GROUP-BASED ASSESSMENT [50%]

a. Deliverable 1: Report [CLO 1, 2, 3, 4]

b. Deliverable 2: Presentation [CLO 1, 2, 3, 4]

c. Deliverable 3: Business, Analysis, and Design Models (StarUML file)[CLO 2, 3, 4]

* Report should be created using the provided report template.

INDIVIDUAL-BASED ASSESSMENT [50%]

d. Oral Communication [CLO 1, 2, 3, 4] [15 Marks]

e. Collaboration [CLO 2, 3, 4] [10 Marks]

f. Follow-up Questions and Discussion [CLO1, 2, 3, 4] [25 Marks]

PROJECT MILESTONES
Milestone Week Deliverable Responsibility Graded
Project Handout Week4 Form Teams, choose topic Teacher & Team No

Milestone 1 Week 6 Answers of Q15 Team Leader & Team No

members
Milestone 2 Week 9 Partial Answers for Q68 Team Leader & Team No
[Only for one sprint/iteration] members
Milestone 3 Week 121 Partial Answers for Q910 Team Leader & Team No
[Only for one sprint/iteration] members
Milestone 4 Week 13 Final Submission and Oral Team Yes
Defense

FINAL SUBMISSION
1. Create a folder named TeamCode_StudentNames (Example: T1_Ahmed_Yousuf_Khalid)
2. Add the report, presentation, and StarUML file to the folder created above
a. Report Name: TeamCode_CaseStudyNumber_Report (Example: T1_Case3_Report)
b. Presentation Name: TeamCode_CaseStudyNumber_Report (Example: T1_Case3_Presentation)
b. StarUML File Name: TeamCode_CaseStudyNumber (T1_Case3)
3. Compress the folder (created in step 1) and submit on BBLearn

Submissions must be student’s original work. Refer to the Academic Misconduct policies and procedures.

GOOD LUCK

CIS2303-Project Description P a g e 4|
 GROUP PROJECT RUBRIC [TASK-SPECIFIC RUBRIC]
Section 1 CLO1: Compare a range of system development methodologies (CAP weight 2%=4 Marks)
Max Awarded Insufficient Emerging Satisfactory Competent Mastering
Criteria
Marks Marks 0-59% 60%-69% 70%-76% 77%-86% 87%-100%

 Inappropriate Some but not all of Most but not all of All of the following: All of the following:
development process is the following: the following:  Appropriate  Rationale for
chosen.  Appropriate  Appropriate development development process
 Selection development development process is chosen. is sophisticated &
rationale is not sound. process is chosen. process is chosen.  Sound extremely well-
 Not properly  Sound  Sound rationale for chosen developed.
referenced. rationale for chosen rationale for chosen development  Rigor is
 Student has an development development process. evident.
Q1. Identify the
accumulation of errors in process. process.  No  Student
suitable development 4 grammar, usage, and  No  No referencing issues. synthesizes
process for the project mechanics that distract referencing issues. referencing issues.  Report is information from
or interfere with  Report is  Report is free of distracting multiple disciplines
meaning free of distracting free of distracting errors in grammar, and sources and
errors in grammar, errors in grammar, usage, and presents them with
usage, and usage, and mechanics clarity.
mechanics mechanics  Report is
free of distracting
errors in grammar,
usage, and mechanics
Subtotal 4
Section 2 CLO2: Create behavioral models to document system requirements (CAP weight 11%=22 Marks)
Awarded Insufficient Emerging Satisfactory Competent Mastering
Marks 0-59% 60%-69% 70%-76% 77%-86% 87%-100%
 No or  Some but  Most but  All  All feasibility
Q2. Conduct the
inappropriate feasibility not all of the not all of the feasibility tests are tests are properly
feasibility study for
4 study is conducted feasibility tests are feasibility tests are properly conducted conducted and
this project
properly conducted properly conducted and explained. explained.
and explained. and explained
Q3. Define, discover, 4  No or  Only one  Two  Two  More than

CIS2303-Project Description P a g e 5 | 11
 inappropriate requirements requirements requirements two requirements
requirements gathering gathering technique gathering techniques gathering techniques gathering techniques
technique is used. is used are used are used are used
 None of the  Sound  Sound  Sound  Rationale for
user requirements and rationale for chosen rationale for chosen rationale for chosen requirements
constraints are requirements requirements requirements gathering techniques
appropriately defined gathering technique gathering techniques gathering techniques are sophisticated &
 Selection  A few of  Some of  Most of the extremely well-
review, document, and rationale is not sound the user the user user requirements developed.
understand the user's  Not properly requirements and requirements and and constraints are  All user
needs and constraints referenced constraints are constraints are appropriately requirements and
for the system by using  Student has an appropriately appropriately defined. constraints are
the requirement accumulation of errors in defined. defined.  Minor appropriately
grammar, usage, and  Minor  Minor referencing issues defined.
engineering
mechanics that distract referencing issues referencing issues  Is free of  Rigor is
techniques
or interfere with  Is free of  Is free of distracting errors in evident.
meaning distracting errors in distracting errors in grammar, usage, and  Student
grammar, usage, and grammar, usage, and mechanics synthesizes
mechanics mechanics  information from
  multiple disciplines
and sources and
presents them with
clarity.

Q4. Create an activity 4  Missing and/ or Some but not all of Most but not all of . No syntactical . No semantic errors.
diagram describing the wrong swimlanes. the following: the following: errors. The AD is well-
behavior of the  Missing and/or  . No  . No  . All formed, consistent,
business process. wrong activities. syntactical errors. syntactical errors. swimlanes are and coherent.
Q5. What is the  Missing and/or  . All  . All identified. . No syntactical
perimeter of the to-be wrong control nodes. swimlanes are swimlanes are  . All
 System errors.
system identified. identified. activities are
perimeter is not . All swimlanes are
 . All  . All identified.
identified. activities are activities are  . All control identified.
identified. identified. nodes are identified. . All activities are
 . All control  . All control  . The identified.
nodes are identified. nodes are identified. system perimeter is . All control nodes are
 . The  . The identified. identified.

CIS2303-Project Description P a g e 6 | 11
 system perimeter is system perimeter is . The system
identified. identified. perimeter is
identified.
 Missing and/or  Some  Most  All  Additional
wrong functional functional functional functional functional
requirements. requirements are requirements are requirements are requirements are
 Missing and/or identified. identified. identified. identified.
wrong non-functional  Some non-  Most non-  All non-  .All non-
requirements. functional functional functional functional
[Rubric for the UCD] requirements are requirements are requirements are requirements are
 Syntactical identified. identified. identified. identified.
errors. [Rubric for the UCD] [Rubric for the UCD] [Rubric for the UCD] [Rubric for the UCD]
 Missing and/or Some but not all of Most but not all of All of the following: All of the following:
Q6. Identify the wrong actors and types. the following: the following:  No  No
functional and non-  Missing and/or  No  No syntactical errors. semantics errors. The
functional wrong granularity level syntactical errors. syntactical errors.  All actors UCD is well-formed,
requirements of the of use cases.  All actors  All actors and their types are consistent, and
to-be system?  Missing and/or and their types are and their types are identified. coherent.
Q7. According to your wrong relationships. identified. identified.  All use  No
answer in Question 1 6 [Rubric for the Product  All use  All use cases are illustrated. syntactical errors.
and 6, describe the Backlog] cases are illustrated. cases are illustrated.  All  All actors
requirements using  Missing and/or  All  All relationships are and their types are
either a product wrong user stories. relationships are relationships are identified. identified.
backlog or a use case identified. identified. [Rubric for the  . All use
diagram. [Rubric for the [Rubric for the Product Backlog] cases are illustrated.
Product Backlog] Product Backlog]  All user  . All
 Some user  Most of the stories are identified. relationships are
stories are identified. user stories are identified.
identified. [Rubric for the
Product Backlog]
 All user
stories are identified
 Any agile
development
software such as Jira
is used
Q8. For each 4  Missing and/or  Some  Most  All  All

CIS2303-Project Description P a g e 7 | 11
 wrong participants. participants are participants are participants are participants are
 Missing and/or identified. identified. identified. identified.
wrong messages.  Some  Most  All  All messages
 Wong message messages are messages are messages are are identified.
types. identified. identified. identified.  All message
 Incoherent and  Some  Most  All message types are valid.
inconsistent scenario. message types are message types are types are valid.  Combined
sprint/iteration, create valid. valid.  Combined fragments are
a system sequence  Combined  Combined fragments are appropriately used
diagram describing the fragments are fragments are appropriately used when needed
behavior of or a user appropriately used appropriately used when needed  Interactions
story/a use case. when needed when needed  Interactions properly implement
 Interactions  Interactions properly implement all scenarios (normal,
properly implement properly implement all the steps defined alternative, error
some of the steps most of the steps in the normal scenarios) defined in
defined in the defined in the scenario (textual the textual
normal scenario normal scenario description of the description of the use
(textual description (textual description use case). case.
of the use case). of the use case).

Subtotal 22
Section 3 CLO3: Create structural models to specify system requirement (CAP weight 6%=12 Marks)
Awarded Insufficient Emerging Satisfactory Competent Mastering
Marks 0-59% 60%-69% 70%-76% 77%-86% 87%-100%
Q9. For each 12  Missing and/or Some but not all of Most but not all of All of the following: All of the following:
sprint/iteration, create wrong classes. the following: the following:  All classes  All classes
a fragment of the  Missing and/or  All classes  All classes are identified. are identified.
domain class diagram wrong attributes. are identified. are identified.  All  All attributes
describing the  Missing and/or  All  All attributes are are identified and
structure of the to-be wrong methods. attributes are attributes are identified and include their data
system.  Missing and/or identified and identified and include their data type.
Q10. Merge/Refine all wrong multiplicities, include their data include their data type.  All methods
fragments to define associations, type. type.  All methods are identified, well
the domain class aggregations,  All methods  All methods are identified, well described, and
diagram. composition, and are identified, well are identified, well described, and include their data
generalization/ described, and described, and include their data types and returns.
specialization. include their data include their data types and returns.  All

CIS2303-Project Description P a g e 8 | 11
 types and returns. types and returns.  All multiplicities,
 All  All multiplicities, associations,
multiplicities, multiplicities, associations, aggregations,
associations, associations, aggregations, compositions, and
aggregations, aggregations, compositions, and generalizations/
compositions, and compositions, and generalizations/ specializations are
generalizations/ generalizations/ specializations are identified.
specializations are specializations are identified.  Low
identified. identified. coupling and high
cohesion.
Subtotal 12
Section 4 CLO4: Create a high-level software architectural design model (CAP weight 6%=12 Marks)
Awarded Insufficient Emerging Satisfactory Competent Mastering
Marks 0-59% 60%-69% 70%-76% 77%-86% 87%-100%
 Inappropriate Some but not all of Most but not all of All of the following: All of the following
architectural pattern is the following: the following:  Appropriate  Rationale for
chosen.  Appropriate  Appropriate architectural pattern architectural pattern
 Selection architectural pattern architectural pattern is chosen. is sophisticated &
rationale is not sound. is chosen. is chosen.  Sound extremely well-
 High-level  Sound  Sound rationale for chosen developed.
Q11. Which architectural design rationale for chosen rationale for chosen architectural pattern.  Rigor is
architectural pattern model is not well architectural pattern. architectural pattern.  High-level evident.
you like to adopt to defined.  High-level  High-level architectural design  High-level
design the to-be  Not properly architectural design architectural design model is well architectural design
system? referenced. model is well model is well defined. model is well defined
Q12. Create a high- 12  Student has an defined. defined.  No  Student
level architectural accumulation of errors in  No  No referencing issues. synthesizes
model of the to-be grammar, usage, and referencing issues. referencing issues.  Report is information from
system. mechanics that distract  Report is  Report is free of distracting multiple disciplines
or interfere with free of distracting free of distracting errors in grammar, and sources and
meaning errors in grammar, errors in grammar, usage, and presents them with
usage, and usage, and mechanics clarity.
mechanics mechanics  Report is
free of distracting
errors in grammar,
usage, and mechanics
Subtotal 12

CIS2303-Project Description P a g e 9 | 11
 Total Group
50
Project Score

INDIVIDUAL ORAL PRESENTATION

STUDENT (1) NAME: ____________________________ STUDENT HCT ID:_______________

Absent Insufficient Emerging Satisfactory Competent Mastering

0-59% 60%-69% 70%-76% 77%-86% 87%-100%
Collaboration  Does not  Participates in  Cooperates  Coordinates both  Coordinates
(10%) participate in the task or is the task, but does not with the group process, processes and products processes and products
so often off the task that cooperate with others but does not coordinate with those of teammates, with those of teammates.
he/she performs. or with the group his or her contributions but does not resolve major  Resolves both
 No contribution process. with those of others. conflicts. major and minor conflicts
to the group goal.  Participates in  Listens  Actively listens. effectively.
discussions. without interrupting.  Gives and  Expresses
 Voices own  Actively receives constructive disagreements honestly
opinion and views. solicits others’ ideas. feedback. but tactfully.
 Remains  Accepts  Adapts  Supports group
focused on the topic. assigned tasks. ideas/process to decisions even if not in
 Completes  Goes along accommodate teammates. total agreement.
some tasks with group consensus.  Seeks consensus.  Compromises
independently.  Builds on  Resolves minor and negotiates to reach
others’ ideas. conflicts effectively. solution.
Oral  Communicates Some but not all of the Most but not all of the All of the following: All of the following:
Communication with a limited sense of following: following:  Communicates  Communicates
(15%) audience and purpose (No  Communicates  Communicates with a clear sense of with a strong sense of
eye contact, no body with a clear sense of with a clear sense of audience and purpose (Eye audience and purpose
language, and no poise) audience and purpose audience and purpose contact, body language, (holds attention with the
 Communicates (Eye contact, body (Eye contact, body and poise) use if direct eye contact,
information and ideas with language, and poise) language, and poise)  Communicates seldom looking at notes)
limited clarity  Communicates  Communicates information and ideas with  Communicates

CIS2303-Project Description P a g e 10 | 11
  Uses language information and ideas information and ideas considerable clarity which information and ideas with
with limited accuracy and with considerable with considerable demonstrates good a high degree of clarity
effectiveness clarity which clarity which understanding of the topic which demonstrates
 Tension and demonstrates good demonstrates good  Uses language excellent knowledge of the
nervousness are obvious; understanding of the understanding of the with considerable accuracy subject.
has trouble recovering topic topic and effectiveness  Uses Language
from mistakes  Uses Language  Uses language  Makes minor with a high degree of
 Presentation with considerable with considerable mistakes, but quickly accuracy and
indicates lack of accuracy and accuracy and recovers from them; effectiveness
understanding of the topic effectiveness effectiveness displays little or no  Student displays
  Makes minor  Makes minor tensions relaxed, self-confident,
mistakes, but quickly mistakes, but quickly  Well-organized with no mistakes
recovers from them; recovers from them; presentation  Presentation is
displays little or no displays little or no polished.
tensions tensions
 Well-  Well-
organized organized
presentation presentation
Follow-up Unable to answer Able to answer some Able to answer most Able to answer all Able to answer all
questions and questions from the but not all questions but not all questions questions from the questions and
discussion examining board. from the examining from the examining examining board. demonstrate a complete
(25%) board. board. understanding of the
study.

FINAL GRADE PROJECT SCORE

STUDENT 1 STUDENT 2 STUDENT 3 STUDENT 4

Total Group Project Score

Total Individual Oral VIVA / Oral
Defense
Final Score

CIS2303-Project Description P a g e 11 | 11