CS5002NI Software Engineering 1st SIT Coursework – 02 Question 2025

CS5002NI Software Engineering Assignment – (Individual)

1. Introduction

This assignment contributes 35% to the overall mark for this module.

2. Specification

The Global Tech Corporation embarked on an ambitious project to develop a next-generation, automated infrastructure system for supporting warehouse management. Global Tech Corporation decides to implement a new inventory management system (IMS) to streamline operations in Nepal.

The absence of Object-Oriented Analysis and Design (OOAD) can lead to several issues, such as systems that are less modular, harder to maintain, less scalable, and more difficult to understand and collaborate on. Unfortunately, due to inadequate system design and analysis, the IMS implementation was ultimately deemed unsuccessful. The warehouse continued to face inefficiencies, financial losses, and customer dissatisfaction.

In response, Global Tech Corporation decided to place a strong emphasis on proper system design and analysis for future projects to avoid repeating these mistakes.

DETAILED SPECIFICATION

The proposed system is to have following functions

Access users to system:

In an inventory system, users—Admin and customer(buyer) register and login to access their specific role.

Purchase Order:

The Add Purchase function allows users to record new purchases of a product from a supplier, while View Purchase lets them review past purchase details. While viewing the product, there should be a provision to compare prices between similar products in case customers want it.

Generate Report:

Report generation is a very essential feature to facilitate decision making for both admin and customers. The Purchase Report tracks new inventory acquisitions, detailing quantities, costs, and suppliers for customers. The Sales Report should facilitate decision making for admin ranging from information of total sales, quantity to the profit and loss made during different points of time.

Sales Management:

Sales Management includes viewing the sales order, viewing delivery methods, address, contact information, dispatching details etc.

Product Management:

Add Product used to input new products in the inventory system, while View Product provides quick access to current stock levels, sales history, and supplier data.

Payment:

There should be an option to make payment for buyers to make payments for the inventories they purchase. The payment data should be securely stored and integrated with inventory management.

Planning, requirements modeling and analysis (65%)

1. Prepare a Work Breakdown Structure as a part of Scope Identification. Also prepare a Gantt Chart showcasing the schedule of work with a reasonably assumed timeline. But please ensure that the Gantt chart is based upon a methodology of your choice and the activities/tasks should be relevant to the methodology chosen.

2. Produce a Use Case Model for the required system – including a Use Case diagram, and High-Level Use Case Descriptions for each Use Case. For two of the Use Cases of your choice, produce Expanded Use Case Descriptions.

Choose one of these expanded Use Case Descriptions to model Collaboration or Sequence diagrams, in 3, below.

3. Explain in words the steps involved in the development of Communication diagram/Sequence diagram from the Use Case model. Produce a Collaboration diagram or a Sequence diagram for the chosen use case description as mentioned above.

4. Draw an activity diagram for the use case description that hasn’t been chosen for the Sequence/Collaboration diagram above.

5. Prepare a table comprising all possible domain classes from all the respective use cases. Produce an Analysis Class diagram showing the domain classes.

Design (35%)

1. You have done several tasks till date (analysis and design diagrams have been done). Now how do you plan to move further in the process of completing the project? You are required to select a methodology that you think is feasible for this project and your explanation of further planning should be relatable to the methodology that you have chosen.

(Note: the further planning should compulsorily include following things:

1. Architectural choice.
2. Design Pattern.
3. Development Plan (that includes tools/resources/programming platforms that are going to be used and priority order of artifacts/features that you have planned tentatively.
4. Testing Plan.
5. Maintenance Plan.

2. Develop some design prototypes for the proposed system for features which are listed in detailed specification.

(Note: the prototypes should cover the major features and at least 15 separate prototypes(UI) need to be shown.