1st SIT Coursework – 02 Question paper Year Long 2024/2025

Module Code: Module Title: Module Leader: Related Post 6BU020+Assessment+Brief++202425 June 9, 2025 Individual Assignment Rubrics V1 (1) June 9, 2025 Individual Case Assignment Brief V11 (1) June 9, 2025 Individual Assignment Rubrics V1 (1) June 9, 2025

CC5002NP Software Engineering Mr. Sandeep Gurung

© London Metropolitan University

PLAGIARISM

You are reminded that there exist regulations concerning plagiarism. Extracts from these regulations are printed overleaf. Please sign below to say that you have read and understand these extracts:

Extracts from University Regulations on Cheating, Plagiarism and Collusion

Section 2.3: “The following broad types of offence can be identified and are provided as indicative examples ….

1. Cheating: including taking unauthorised material into an examination; consulting unauthorised material outside the examination hall during the examination; obtaining an unseen examination paper in advance of the examination; copying from another examinee; using an unauthorised calculator during the examination or storing unauthorised material in the memory of a programmable calculator which is taken into the examination; copying coursework.
2. Falsifying data in experimental results.
3. Personation, where a substitute takes an examination or test on behalf of the candidate. Both candidate and substitute may be guilty of an offence under these Regulations.
4. Bribery or attempted bribery of a person thought to have some influence on the candidate’s assessment.
5. Collusion to present joint work as the work solely of one individual.
6. Plagiarism, where the work or ideas of another are presented as the candidate’s own.
7. Other conduct calculated to secure an advantage on assessment.
8. Assisting in any of the above.

Some notes on what this means for students:

1. Copying another student’s work is an offence, whether from a copy on paper or from a computer file, and in whatever form the intellectual property being copied takes, including text, mathematical notation, and computer programs.
2. Taking extracts from published sources without attribution is an offence. To quote ideas, sometimes using extracts, is generally to be encouraged. Quoting ideas is achieved by stating an author’s argument and attributing it, perhaps by quoting, immediately in the text, his or her name and year of publication, e.g. “e = mc² (Einstein 1905)”. A reference section at the end of your work should then list all such references in alphabetical order of authors’ surnames. (There are variations on this referencing system which your tutors may prefer you to use.) If you wish to quote a paragraph or so from published work then indent the quotation on both left and right margins, using an italic font where practicable, and introduce the quotation with an attribution.

School of Computing, FLSC

CONTRACT CHEATING

Contract cheating (also known as assessment outsourcing, commissioning or ghost writing) is when someone seeks out another party, or AI generator service, to produce work or buy an essay or assignment, either already written or specifically written for them or the assignment to submit as their own piece of work.

Contract cheating undermines the integrity of the academic process and devalues the qualifications awarded by the university. Students are reminded that academic integrity is a fundamental principle of our institution. Engaging in contract cheating not only impacts the individual’s academic record but also the reputation of the university.

Students are encouraged to seek support if they are struggling with their coursework. The university offers a range of resources, including academic counseling, tutoring services, and workshops on study skills and time management. Utilizing these resources can help students achieve their academic goals without resorting to dishonest practices.

Penalty:

• Failure in the Module: The student must re-register for the same module, and the re-registered module will be capped at a bare pass.
• Ineligibility to Continue on the Course: Where re-registration of the same module, or a suitable alternative, is not permissible, the student will not be able to continue on the course. Additionally, the following penalty will be applied to the student’s final award:
  • Undergraduate Honors: The student’s final classification will be reduced by one level.
  • Unclassified Bachelors: Downgraded to Diploma in Higher Education.
  • Foundation Degree: Distinction downgraded to Merit; Merit downgraded to Pass; Pass downgraded to Certificate in Higher Education.
  • Masters: Distinction downgraded to Merit; Merit downgraded to Pass; Pass downgraded to Postgraduate Diploma.

Reporting and Consequences:

Instances of contract cheating will be thoroughly investigated, and students found guilty will face the penalties outlined above. It is the responsibility of every student to ensure that their work is their own and to avoid situations that could lead to accusations of academic misconduct.

By adhering to these standards, students contribute to a fair and equitable academic environment, ensuring the value and recognition of their qualifications are maintained.

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

1. Access users to system:

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

1. 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.

1. 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.

1. Sales Management:

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

1. 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.

1. 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.

Marking Scheme

MILESTONE BREAKDOWN

MILESTONE 1 (Week 18)

Planning Diagrams

• WBS and Gantt Chart

OOAD Analysis

• Use Case Diagram and Expanded Level Descriptions.

MILESTONE 2 (Week 21)

Report

• Introduction

Diagrams

• Sequence Diagram/Communication
• Activity Diagram

MILESTONE 3 (Week 24)

Report

• Conclusion

Class Diagram

Description of further development section

• (Implementation of Agile approaches optimal choice of architecture and design patterns for the system.)

Prototypes

Final Submission (12th May)

END