RMIT Classification: Trusted

COSC 2398 SE Fundamentals

Group Project (Stage1)

Due Date

This assignment is due in Week 10. Exact due date will be as published in
Canvas>Assignments section.

General overview

This assessment is the first stage of a semester-long project. The project is to

analyse, and design custom software based on the given set of client requirements.
The software is to be built iteratively and incrementally following the modern
software engineering approach. This project is to be completed in two stages Stage1
and Stage 2. Each stage being built on its predecessor (previous stage).
You will work on this project in teams of 3-4 students. You must define and
document each team member responsibilities and submit to your teacher. First stage
involves brainstorming and requires lots of discussions with your team members
and clarifying any questions with your client (in our case it’s your teacher)

Client requirements
Please note that these requirements, like many requirements that come from clients may
contain ambiguities, contradictions, and incorrect information. As well there may be some
important information that is missing. You must analyze the requirements and identify these
problems. You will need to clarify these points by interviewing the client (your teacher).

Case Study

UniOne has sought your help to develop a Library Operations System (LOS). This
is a software application which is to be employed for automating the library
operations.
It will allow the librarian to maintain the information about books, magazines,
CD/DVDs (i.e. digital media) and library users.
Furthermore, it is envisioned that this software facilities searching for items,
browsing the catalog, checkout of items, item returns, reservations, reservation
cancellations, etc.
Any user intending to borrow must get registered in the system initially. The users
can search for any item in the library by using the 'search option' from the menu.
If the user finds the item they are searching for in the library, they can check-out the
item from the library.
 RMIT Classification: Trusted

If the study material is not available in the library at the moment, the user can make
a reservation for that item. The moment the item is available, the user who first
reserved for that item is notified first.
If the user checks out the item from the library, the reservation gets cancelled
automatically. The reservation can also be cancelled through an explicit
cancellation procedure initiated by the user or librarian.
The librarian is an employee of the library who interacts with the borrowers whose
work is supported by the system.
The system allows the librarian to perform the following functions with a lot of
ease:
 Create records for new titles in the catalog.
 Update titles in the catalog.
 Delete information about titles.
 Update/Delete Borrowers.
 Look up items on loan and reservations in the system.
The library system can run on popular web-browser platforms like Edge, Chrome,
Firefox, etc. It must be easily extendable with new functionality.

Please refer to client/stakeholder discussion notes for more details

Instructions to Students

1. Form a team of up 3-4 (preferably four) students from within your course
section. Do not form groups with students who attend a different Tutorial or
Laboratory session (i.e. different section)
2. Go to section marked Project Groups and register your teams. Your teacher will
explain how to accomplish this in class.
3. Each team will be invited to a scheduled meeting with their teacher for about 10-
15 minutes. Every member of the team MUST attend this meeting. The absent
member will risk losing 50% of the marks reserved for Stage 1.

What happens during this meeting?

1. Members of your team will be randomly asked to demonstrate/explain any

aspect of work done on the project. If the member is unable to explain or
demonstrate the work, he/she will immediately lose 3 marks. Explanations
about having worked on another aspect of the project will not be acceptable,
since it is expected that as part of the project team you understand ALL the
work has been done on the project, not only the aspect you focused on.
2. Your teacher will provide feedback on any errors or omissions and make
suggestions on how you can improve your work/documentation.
 RMIT Classification: Trusted

Assignment requirements

In stage 1 you must analyse client requirements, create a requirements document

(SRS), analyze, and design your application. You should submit the following
documents (see some details below the list). The screen dump of this interface and
description of its functionality may be included in your team requirement
document.

Only one submission per team is required.

Submission includes (see details below)

1. SRS document
2. Use Case model

The following is a description of important parts of submission.

SRS document (12 marks)

 Divide the Software Requirements Specification into 3 different sections
as documented:

 Section 1 – Introduction should include:

o Purpose of the document
o Scope of Project
o Glossary of terms used in the document
o Overview of the document
o References if any
 Section 2 – Overall System Description should include:
o System Environment: A block diagram view with brief explanation
of the system
o Software Product Functions: At least 6 important and relevant
Use-cases (functions that are core to the software solution) identified
using the Client/Stakeholder discussion sheets provided and
documented as shown in the sample SRS provided.
o User Characteristics: Relevant to the case study provided. (You
may refer the sample SRS document provided to gain some idea.)
o System Constraints: Relevant to the case study provided and as can
be found in the Client/Stakeholder discussion sheets provided.
o Assumptions and Dependencies: Relevant to the case study
provided and as can be derived from the Client/Stakeholder
discussion sheets provided.
 Section 3 – Requirements Specification should include:
o External Interface Requirements: Relevant to the case study
provided and as can be derived from the Client/Stakeholder
discussion sheets provided.
 RMIT Classification: Trusted

These consist of:

 User Interfaces
 Hardware Interfaces
 Software Interfaces
 Communication Interfaces
o Functional Requirements: Fully dressed description of use cases
identified in Section 2 above. (This must be well-documented
otherwise you risk losing up to 6 marks)
o Non-functional Requirements: Relevant to the case study provided
and as can be found in the Client/Stakeholder discussion sheets
provided. The non-functional requirements should be further
decomposed and placed under appropriate sub-sections such as
Performance requirements, Design constraints, Logical database
requirements, Software Quality Attribute requirements (further
decomposition possible)

3. Analysis Models (8 marks)

The analysis documents should include such UML diagrams as
1. Use case diagrams, showing the actors and relevant use cases for the
system. You must depict inclusions and extensions, relevant to the use-cases
documented in the SRS. Your use case diagrams must comply with your
other documentation: SRS and domain diagrams.

Basic Marking Criteria

This assignment is worth 20% of total mark for this course. The total mark for a
team then will be calculated as follows:

SRS document: 12
----------------------------------------------------
Analysis: 08

Complete Use Case Model: 08

----------------------------------------------------

Total mark: 20.

Submission
Only one submission for a team is accepted.

You need only to submit two separate files in fulfillment of the requirements of this
assessment via Canvas\Assignments\ Project Stage 1.
 RMIT Classification: Trusted

Do not ZIP or ARCHIVE your files and submit your work.