Reference no: EM132524440

ISYS2002 Introductory Systems Analysis and Design - Curtin University

Learning Outcome 1: Apply appropriate problem solving processes based on logical and critical thinking and systems modelling to produce the system's scope, analyse system requirements and design potential information system solutions.

Learning Outcome 2: Prepare a business case for a proposed business problem solution and produce a suitable system specification report.

Case Study - Personnel Self-Service System (PSS)

Assignment Requirements

Unfortunately, Tom has left the organisation and you, as a trainee systems analyst in the IT department, have been asked by your manager to finish the job. By analysing the information gathered from the interviews and using appropriate fact-finding techniques, prepare a Functional Requirements Report

The format for the report is detailed below.

Part 1. Needs and/or Problem description, and proposed solution (system capabilities) of new system.

Part 2. Description of functionality of the new system. You must provide the major (must have) use cases and their descriptions for the new system based on the requirements identified in the case study. The major (must have) use cases should provide the functionality to address the needs/problems identified in part 1 above.
• You must provide a Use-Case Glossary that shows the name of each use case, a brief description of the use case and the actors for the use case. Look at the assignment example (in the assignment folder on BB) for an example of a brief description of a use case.
• You must number your use cases in the glossary.
• The use cases should be presented in a "logical" sequence.

Part 3. Description of data requirements of the new system. You must provide:
a. An ER Diagram
b. The name, description and an example of the data stored in each of the attributes for each entity of interest to the system and relationship (where applicable). You can make some reasonable assumptions when describing the attributes. You must indicate which attribute is the identifier for each entity.

Part 4. Design input screen(s) for 3 of the major (must have) use cases (identified in part 2 above) that is used to record/update information. Indicate clearly which use case in part 2 that the input screen(s) is for. Provide the use case name, a brief description and associated attributes before presenting the input screen.
a. Indicate which data entry control is used for each input field and which fields are display only fields.
b. List the flow of activities i.e. the key steps followed for the dialog with a written description of what the user and system do at each step (see example on BB).

Part 5. Design output reports and corresponding input screens (where applicable) for 3 of the use cases (identified in part 2 above) where Personnel was the "actor".

Part 6. Assignment plan and progress reports signed by your group and your tutor.

Attachment:- Case Study - Personnel Kiosk System.rar