Written assessment

APA 6th style referencing and 2000 words assessment with case study ( Online Student Enrolment System at ABC University ).MIS605_Assessment 1_Case Study Page 1 of 1

Online Student Enrolment System at ABC University

ABC University (ABCU) is seeking to develop an online student enrolment system (the System)

whereby the students would be able to enrol themselves into eligible subjects at the beginning of each

trimester and pay their tuition fees online. You have been hired as the Business Analyst for this project.

Founded in Sydney in 2013, ABCU has experienced a remarkable growth in student numbers in recent

years and has opened new campuses in three other Australian cities including Melbourne, Brisbane

and Adelaide. ABCU currently has 50,000 students across their four campuses with an estimated 5000

student in-take in each trimester. This phenomenal growth in their student numbers has necessitated

the need for an online student enrolment system. Once developed, this system will replace the manual

enrolment process that is currently in place. The current manual enrolment process is labour-

intensive, error-prone, and rather inefficient as it requires the Student Enrolment Officers to manually

enrol each student into the subjects upon the receipt of a study plan from the students.

The Pro Vice Chancellor (Learning and Teaching) envisage an online student enrolment system which

would allow students to complete their enrolments and tuition fee payments before the Census date.

The System should not only enable Student Enrolment Officers of each School to create, edit and

remove Courses offered by their School but also to create, edit and remove core subjects and electives

offered in each course. The students should be able to access the system through a device of their

choice (e.g. desktop web browser, mobile phone or tablet app).

Most subjects would have pre-requisites that must be satisfied before the students are eligible to

enrol in the subject. It would be the responsibility of the Program Directors to provide and update the

relevant course and subject information including the descriptor, availability (i.e. whether a subject or

a course is offered in a certain trimester) and the prerequisites.

The Timetabling Officers may also create, edit and remove timetables for each available Subject

through the new System. Each campus will hold multiple classes for the same subject. A Subject is

offered in the form of classes. Each campus may offer multiple classes for the same Subject.

Once logged into the System, students should be able to view all the available subjects, enrol in and

drop subjects. The System will detect timetable clashes and prevent students from enrolling into

subjects that clash.

The System should not let students to enrol in too many or few subjects unless they have an increased

or reduced study load approved by the Student Enrolment Officer. Once the enrolment has been

completed theMIS605_Assessment 1_Brief_Written Assessment Page 1 of 7

Task Summary

In response to the issues raised in the ‘online university enrolment system’ case study provided,
identify the functional and non-functional requirement for an online enrolment system and build and
document a set of use cases for that system.

Context

Requirement analysis techniques and skills are of fundamental importance to a Business Analyst, who
is often required to help business users in terms of identifying what they really need in their new
systems. This assessment allows you to enhance your requirement analysis techniques and skills by
capturing the business requirement of a system, identify “what” the proposed system will do, “how”
the system will perform those tasks, and communicate the identified requirement through a set of
use case diagrams and their associated documentations.

ASSESSMENT 1 BRIEF

Subject Code and Title MIS605 Systems Analysis and Design

Assessment Written assessment

Individual/Group Individual

Length 2000 words

Learning Outcomes The Subject Learning Outcomes demonstrated by successful
completion of the task below include:

a) Identify, critically evaluate and recommend information
systems solutions for inefficiencies in business processes,
procedures and work practices using data and process
modelling techniques.

b) Formulate, validate and document business requirements
for a medium-scale information system development
project and effectively communicate these requirements to
the stakeholders.

c) Demonstrate the ability to effectively analyse, design and
develop information systems using Unified Modelling
Language (UML) models.

Submission Due by 11:55pm AEST Sunday end of Module 3.1

Weighting 30%

Total Marks 100 marks

MIS605_Assessment 1_Brief_Written Assessment Page 2 of 7

Instructions

1. Please read the attached MIS605_ Assessment 1_Case Study. Note that every piece of

information provided in the following case serves a purpose.

2. Once you have completed reading the case study. Please answer the following questions:

Question 1.

(a) Who are the stakeholders in this project? Please list at least four stakeholders. (2 marks)

(b) Who are the Actors in this System? Please list at least four actors (4 mark)

Question 2.

Identify and list at least TEN (10) major functional requirements for the System. (20 marks)

Question 3.

Using your own experience with similar online student enrolment systems and the information

provided in the case study, identify and list at least FIVE (5) non-functional requirements for the

System. Explain and justify each non-functional requirement. (20 marks)

Question 4.

Using your own experience with similar online student enrolment systems and the information

proEnterprise Architect

Requirements Engineering

Version 1.0

Date: 2/05/2016

Author: Sparx Systems & Stephen Maguire

CREATED WITH

Table of Contents

Requirements 4
Introduction 7
Meet the Requirement Tools 9

Specification Manager 10
Relationship Matrix 12
Requirement Properties 14
Requirements Diagram 16
Scenario Builder 18
Baseline Tool 20
Traceability Window 22
Dashboard Diagrams 24
The MDG Link for DOORS Add-In 26

Requirements Overview 27
What are Requirements 30
Levels and Types of Requirements 31
Characteristics of Good Requirements 35
Business Context for Requirements 40
Requirements Diagram 44
Creating and Viewing Requirements 48

Requirements Development 53
Elicitation 55

User Observations 56
Stakeholder Workshops 57
Creating Requirements 62

External and Internal Requirements 63
Using the Specification Manager 65
Requirement Properties 66
Color Coded Requirements Status 68
Displaying Properties on a Diagram 70
Import Requirements 73
Move Requirement External 78
Move Requirements Internal 79

Recording Requirement Types 80
Analysis 81

Models Used to Document Requirements 82
Requirements Naming and Numbering 84
Model Assumptions and Constraints 88
Create a Glossary 90
Create a Domain Model 91
Model the User Interface 93
Prioritize the Requirements 94

Specification 97
Specify Quality Attributes 98
Requirement Sources 100
Elaborate the Requirements 102

Validation 104
Derive Test Cases 105
Review Requirements 106

Requirements Management 109
Tracing Requirements 110

Tracking Requirements 113
Managing Changing Requirements 115
Impact Analysis of Changes 118
Requirement Volatility 120
Requirements Reuse 122

Requirements Documentation 124
Project Glossary 125
Software Requirement Specification 126
Use Case Report 127
Data Dictionary 129

Requirement Processes and Standards 130
Agile Requirements Processes 131
Business Analysis Body of Knowledge (BABOK) 133
UML Requirements 138
SysML Requirements 139

MDG Link for DOORS 140
Getting Started 142
Create a Link to a DOORS Module 143
Export Requirements to DOORS 147
Import Requirements from DOORS 152

Additional Requirements Tools 157
Auto Names and Counters 158
Import and Export Spreadsheets 160
Requirements Checklist 162
Documentation 164
Glossary 166
Auditing 168
Element Discussions 170
Maintenance Items 172
Team Reviews 173

Enterprise Architect User Guide – Requirements Engineering 2 May, 2016

Requirements

The field of requirements engineering is one of the most critical disciplines in the solution development
lifecycle and has a documented impact on the success of projects.

Requirements Development

This comprises all the activities and tasks associated with discovering, evaluating, recording, documenting
and validating the requirements for a particular project. Requirements are discovered, analyzed, specified and
verified. Enterprise Architect has a wide range of tools and features to assist the analyst as they develop
requirements. The center piece for requirements deveACME Phase 2(c) RGA
Enabling External User

Functionality

Version 6.1

Alvin J. Alexander
http://www.devdaily.com

Jan. 28, 2004

Contents

1 Introduction 7

2 Assumptions 9
2.0.1 Application Mode Assumptions . . . . . . . . . . . . . 10
2.0.2 User Interface Assumptions . . . . . . . . . . . . . . . 10
2.0.3 Documentation, Help System, and Graphics Assump-

tions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.0.4 Database Assumptions . . . . . . . . . . . . . . . . 11
2.0.5 Database Service Assumptions . . . . . . . . . . . . . 12
2.0.6 Testing Assumptions . . . . . . . . . . . . . . . . . . . 12

3 Requirements 14
3.1 External User Login and Access Control Requirements . . . . 14

3.1.1 Access Control Requirements, General Behavior . . . 14
3.1.2 Access Control Requirements, Security is not Enabled 15
3.1.3 Access Control Requirements, Security is Enabled . . 16
3.1.4 Initial database information . . . . . . . . . . . . . . . 19
3.1.5 External user logins . . . . . . . . . . . . . . . . . . . 19

3.2 Database Requirements . . . . . . . . . . . . . . . . . . . 20
3.2.1 Database Selection . . . . . . . . . . . . . . . . . . 20

3.3 Documentation Notes, Errata . . . . . . . . . . . . . . . 20

4 Use Cases 22
4.1 External User Login . . . . . . . . . . . . . . . . . . . . . . . 24

4.1.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1.2 Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1.3 Pre-Conditions . . . . . . . . . . . . . . . . . . . . . . 24
4.1.4 Access Control is not Enabled . . . . . . . . . . . . . 24
4.1.5 Alternative Path #1, Access Control is Enabled . . . 25

Contents

4.1.6 Alternative Path #2, Security Enabled, Administra-
tor Logs In . . . . . . . . . . . . . . . . . . . . . . . . 27

4.1.7 Alternative Path #3, User Selects a Different Database
During Login . . . . . . . . . . . . . . . . . . . . . . 28

4.1.8 ”Used” Use Cases . . . . . . . . . . . . . . . . . . . . 28
4.1.9 Other Requirements . . . . . . . . . . . . . . . . . . . 29

4.2 Add User Account . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.2 Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.3 Pre-Conditions . . . . . . . . . . . . . . . . . . . . . . 30
4.2.4 Basic Path: Create a New User Account . . . . . . . . 30
4.2.5 Post-Conditions . . . . . . . . . . . . . . . . . . . . . . 31
4.2.6 ”Used” Use Cases . . . . . . . . . . . . . . . . . . . . 31
4.2.7 Other Requirements . . . . . . . . . . . . . . . . . . . 31

4.3 List User Accounts . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.2 Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.3 Pre-Conditions . . . . . . . . . . . . . . . . . . . . . . 32
4.3.4 Flow of Events: Administrator . . . . . . . . . .[YourProject] Requirements Specification

[YourProject] Requirements Specification

Version 1.0

September 24, 2013
Use this Requirements Specification template to document the requirements for your product or service, including priority and approval. Tailor the specification to suit your project, organizing the applicable sections in a way that works best, and use the checklist to record the decisions about what is applicable and what isn’t.
The format of the requirements depends on what works best for your project.

This document contains instructions and examples which are for the benefit of the person writing the document and should be removed before the document is finalized.
To regenerate the TOC, select all (CTL-A) and press F9.

Table of Contents

3
1.
Executive Summary

31.1
Project Overview

31.2
Purpose and Scope of this Specification

3
2.
Product/Service Description

32.1
Product Context

32.2
User Characteristics

32.3
Assumptions

32.4
Constraints

42.5
Dependencies

4
3.
Requirements

53.1
Functional Requirements

53.2
User Interface Requirements

53.3
Usability

63.4
Performance

6
3.4.1
Capacity

6
3.4.2
Availability

6
3.4.3
Latency

63.5
Manageability/Maintainability

6
3.5.1
Monitoring

6
3.5.2
Maintenance

6
3.5.3
Operations

73.6
System Interface/Integration

7
3.6.1
Network and Hardware Interfaces

7
3.6.2
Systems Interfaces

83.7
Security

8
3.7.1
Protection

8
3.7.2
Authorization and Authentication

83.8
Data Management

83.9
Standards Compliance

83.10
Portability

9
4.
User Scenarios/Use Cases

9
5.
Deleted or Deferred Requirements

10
6.
Requirements Confirmation/Stakeholder sign-off

11
APPENDIX

11Appendix A.
Definitions, Acronyms, and Abbreviations

11Appendix B.
References

11Appendix C.
Requirements Traceability Matrix

13Appendix D.
Organizing the Requirements

1. Executive Summary
1.1 Project Overview
Describe this project or product and its intended audience, or provide a link or reference to the project charter.
1.2 Purpose and Scope of this Specification
Describe the purpose of this specification and its intended audience. Include a description of what is within the scope what is outside of the scope of these specifications. For example:

In scope

This document addresses requirements related to phase 2 of Project A:

· modification of Classification Processing to meet legislative mandate ABC.

· modification of Labor Relations Processing to meet legislative mandate ABC.

Out of Scope

The following items in phase 3 of Project A are out of scope:

· modification of Classification Processing to meet legislative mandate XYZ.

· modification of Labor Relations Processing to meet legislative mandate XYZ.

(Phase 3 will be considered in the development of the requirements for Phase 2, but the Phase 3 requirements will be documented separately.)

2. Product/Service Description
In this sectionZachman Framework gives systems analysis context

STAKEHOLDER IDENTIFICATION

Reading use case diagram with Include
relationship

place
phone call

cellular
network

user

receive
phone call

place
conference

call

receive
additional

call

use
scheduler

Cellular Telephone

Use-Case Diagram CaseOrganisation Evolution

AGILE Development Overview

AGILE Development Overview
Agile Four Values

AGILE Development Overview
The 12 Principles of the Agile Manifesto

AGILE Development Overview
The Agile Mindset

AGILE Development Overview
Many different types of Agile techniques

AGILE Development Overview
System Development Life Cycle

AGILE Development Overview
Iteration and Flow Based Agile

AGILE Development Overview
Life Cycle

AGILE Development Overview
Managing Uncertainty

AGILE Development Overview
The Continuum of Change

AGILE Development Overview
Agile Case Studies

https://www.scrumatscale.com/case-study-library/

https://image.slidesharecdn.com/teambuildinginagileteamsmakesense-170112060420/95/team-building-in-agile-teams-make-sense-but-why-12-638.jpg?cb=1490760957605 Systems Analysis and Design

Trimester 3 – Lecture 2

Zachman Framework gives systems analysis context

Mapping Technology to Support Processes and Activities

Systems Development Lifecycle

Project Management Overview

We offer the best custom paper writing services. We have done this question before, we can also do it for you.

Why Choose Us

How It Works

Recent Posts