Team Developers

Requirement Analysis

Overview

♦ This is our second blog on activity monitoring regarding requirement analysis. Today we are going to discuss about

1.Requirements

2.User stories

3.Use case diagram

1.Requirements

♦ The requirements are the customer expectations from the application.

♦ We have gathered all the requirements from the customer by personal team meetings, also through the group meetings within the team and by discussions using SNS.

♦ By all these discussions we have come up with different user stories which form the structure of Requirements.

The requirements are of two types:-

a.Functional Requirements

♦ Each user should register the app by using unique Username.

♦ In functional requirements, the system design is discussed.

b.Non-Functional Requirements

♦ As we know the app should not exceed 512MB.

♦ The system must be developed in Java and should run in the Oracle JVM 1.6.

♦ User guidance must be provided in the settings.

2.User stories

As a user:

♦ I want an app to track my daily activity.

♦ I should be able to customize my GUI by adding categories.

♦ I should be able to color code each and every category according to my desire.

♦ I should be able to add sub-categories within the main categories.

♦ I should be able to set a fixed timetable for a certain period of time.

♦ I should be able to customize the title for each category and subcategory. So, that I can Understand and recognize them later.

♦ I should be able to add date and time when adding an activity. so,that i can have Timestamp.

♦ I should be able to delete my wrong entries.

♦ I should be able to see my summary of my activities each week.

♦ I should be able to use my app in Offline mode.

♦ I want my app to be secure by having a security code.

3.Use case diagram

A use-case diagram is the simplest representation of a user’s interaction with the system which shows the relationship between the user and the different use-cases where the user is involved actually.

How did you get your requirements?

We had three meetings with our customer until now to know the exact requirements, specifications to develop the application.

The customer has prioritized Requirements into three categories

1.Essential Requirements

2.Necessary Requirements

3.Desired Requirements

Our team have discussed accordingly through the requirements and prioritized them.

How did your team analyze requirements?

♦ By visualizing user stories and discussing within our team in group meetings.

♦ Interaction with Customer in weekly meetings.

♦ Brainstorming sessions.

♦ Discussing out the problems with team members and Google.

How did your team specify requirements? How did you map requirements to user stories/use case?

♦ We specified our requirements with our customer and within our team.

♦ Also with help of use case diagrams we are able to specify the requirements by prioritizing them accordingly.

 How did your team identify wrong assumptions? 

♦ For example:-

♦ Within our team group meetings and discussions, we thought that we have to specify the entry categories within the system. We also thought that it should be an online platform only.

♦ But after meeting the customer he specified that it should be customizable and operate also in an offline environment.