Systems Analysis and Design

• 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 CLO5 Total
Marks Allocated 100
Marks Obtained

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 make sure their needs are being met;
• Define an analysis model using different UML diagrams and respecting a 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
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)
  5. Applying the analysis and design techniques following a specific development process (Q13)
    QUESTIONS
    Use STARUML and JIRA to answer the questions from 4 to 12. Document each question by screenshots of diagrams and/or product backlogs.
  6. Which methodology would you like to adopt for this project? Justify your choice by listing 2 arguments.
  7. Conduct the feasibility study for this project.
  8. 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.
  9. Create an activity diagram describing the behavior of the business process.
  10. What is the perimeter of the to-be system?
  11. Identify the functional and non-functional requirements of the to-be system?
  12. According to your answer in Question 1 and 6, describe the requirements using either a product backlog or a use case diagram.
  13. For each sprint/iteration, create a system sequence diagram describing the behavior of or a user story/a use case.
  14. For each sprint/iteration, create a fragment of the domain class diagram describing the structure of the to-be system.
  15. Merge/Refine all fragments to define the domain class diagram.
  16. Which architectural style you like to adopt to design the to-be system?
  17. Create a high-level architectural model of the to-be system.

REPORT AND PRESENTRATION STRUCTURE
REPORT 50%
The Project is done by 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. The following is a list of what is expected for deliverables. Feel Free to add any sections that you want.

CLO Aim Deliverable Content
Report structure description • Cover page
• Table of Content
• Table of Figures
• Introduction
• Answers of all questions
• Conclusion listing the individual student reflections
• References
CLO1: Compare a range of system development methodologies Choice of Software Development process • Provide answer to question 1:

  1. Which methodology would you like to adopt for this project? Justify your choice by listing 2 arguments.
    CLO2: Create behavioral models to document system requirements
    Specification –An explanation of the problem to be solved in terms of business process.
    Requirements Analysis and Definition is the first stage in the systems analysis and design. This stage breaks down functional and non-functional requirements to a basic design view to provide a clear system development process framework. The focus is to describe the behavioral models • Provide answers for questions 2 to 8:
  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.

Sample Solution

find the cost of your paper

This question has been answered.

Get Answer