- Which methodology would you like to adopt for this project? Justify your choice by listing 2 arguments.
- Conduct the feasibility study for this project.
- 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.
- Create an activity diagram describing the behavior of the business process.
- What is the perimeter of the to-be system?
- Identify the functional and non-functional requirements of the to-be system?
- According to your answer in Question 1 and 6, describe the requirements using either a product backlog or a use case diagram.
- For each sprint/iteration, create a system sequence diagram describing the behavior of or a user story/a use case.
- For each sprint/iteration, create a fragment of the domain class diagram describing the structure of the to-be system.
- Merge/Refine all fragments to define the domain class diagram.
- Which architectural style you like to adopt to design the to-be system?
- Create a high-level architectural model of the to-be system.
Sample Solution