Reference no: EM131938361

ASSIGNMENT: Applications Modelling and Development- Requirements and Modelling

Statement

Campus Life are a group on campus that are responsible for managing the experience that students have at Macquarie University. An extract from their website: "to provide higher levels of campus services and support for both students and staff"

Campus Life have recently received a proposal to create a system called "Macquarie University Dating System" (MUDS)*** to provide a way for students at the university to connect with other like-minded students. Campus life are hesitant, but would like to investigate what such a system might look like. You have been tasked with going through the initial description and providing some details about the features and processes that MUDS would have.

An extract from the proposal:

Macquarie University students do not automatically have an account created in MUDS. A students can optionally register to MUDS and start to use its features. In order to register for a MUDS account, the student would need to register their details and validate their account with a connection to eStudent. The reason for this is to cross-check if the student is currently enrolled, and is also who they say they are.

Students can get MUDS to search for potential matches to other students and list any matches. From those matches, a student can request to connect with students they match with. Once a student sends a connection request, MUDS would generate and send a notification using the MQ Notification System (MQNS). When a request comes through, students can view it, and then accept or reject the request. Students also get notified when their request has been accepted.

Students have an option to upgrade to a premium account which will unlock extra features. However, the student will need to pay for this service through the MQ Financial Services System (MQFSS). MUDS does not deal with finances, but can send details for MQFSS to pass on new costs to the student. Students with premium account could choose to downgrade to a general account at any time. Students also can choose to make their account inactive if they no longer want to be searchable, or if they are going to have a semester off / have graduated.

Students can report abuse which would send a notification for staff to review the case. All notifications are sent through MQ Notification System (MQNS). When an abuse report comes through, A MUDS Manager can generate and view an activity report for the account to investigate further and possibly consider disciplinary action.

Students cannot delete their account directly; this is important especially in the case reported accounts. Students can request for their account to be deleted, but the request will need a MUDS Staff member to approve it before the account gets completely removed. When an account deletion comes through, MUDS Staff can approve or reject account deletion.

Task Descriptions

Your tasks in this assignment are as follows:

Task 1: Requirements elicitation

Q1) What are the different requirements gathering techniques that you would use to find out more about the problem? Justify your choices

Q2) Outline a strategy (of between 2-4 requirements gathering phases) and detail which techniques you would use in each phase, and what data you would use from previously gathered information. Justify your selection.

Task 2: Requirements specification and UML modelling.

Q3) Write two user scenarios that would describe a typical usage session (one from a premium account student's perspective and another from MUDS manager's perspective).

Q4) Provide at least three user stories for three different actors.

Q5) Write two functional requirements for the proposed system.

Q6) Write two non-functional requirements for the proposed system.

Q7) Draw a Context Diagram (Level 0 DFD) for MUDS.

Q8) Draw a Use Case Diagram for MUDS based on the problem statement and extract Also: You need to add two more use cases for a premium account student and add that to your diagram. Please add few sentences underneath the diagram explaining what the newly added use cases are.

Q9) Write two use case descriptions - one description for a use case from the problem statement and another for one of the use cases you created.

Q10) Draw a Sequence Diagram for either one of the use case descriptions from Q8 (be sure to select a use case that has at least one actor, and a minimum of 3 entity objects (As lifelines) in the sequence diagram.

Q11) Draw an entity-class diagram for the entire problem statement.

Q12) Draw a State diagram for one of the classes in your class diagram.