CS5002NISoftwareEngineeringY24_25AutumnMainSit20GW1QP_00a1d71b-b03f-4688-b4b1-0a89b0f8fe7f_93444_

1^st SIT COURSEWORK 1 QUESTION PAPER Year Long 2024/2025

Module Code: CS5002NI Module Title: Software Engineering Module Leader: Mr. Rubin Thapa (Islington College)

Coursework Type: Groupwork Coursework This coursework accounts for 20% of your total module Weight: grades. Submission Date: First Milestone: Tuesday, 26 November 2024 Second Milestone: Monday, 16 December 2024 Third Milestone: Tuesday, 24 December 2024 Final Deadline: Thursday, 9 January 2025 When Coursework Week 04 is given out: Submission Submit the following to Islington College’s MySecondTeacher Instructions: portal before the due date (before 01:00 PM on the due date): • Soft copy (Group.pdf file in .pdf format) Warning: London Metropolitan University and Islington College take Plagiarism seriously. Offenders will be dealt with sternly.

© London Metropolitan University

1

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

(i) 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.

(ii) Falsifying data in experimental results.

(iii) 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.

(iv) Bribery or attempted bribery of a person thought to have some influence on the candidate’s assessment.

(v) Collusion to present joint work as the work solely of one individual. (vi) Plagiarism, where the work or ideas of another are presented as the candidate’s own. (vii) Other conduct calculated to secure an advantage on assessment. (viii) 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

2

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:

o Undergraduate Honors: The student’s final classification will be reduced by one level.

o Unclassified Bachelors: Downgraded to Diploma in Higher Education.

o Foundation Degree: Distinction downgraded to Merit; Merit downgraded to Pass; Pass downgraded to Certificate in Higher Education.

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

3

1. Introduction

This assignment contributes 20% to the overall mark for this module and involves group work. You are expected to form groups of 5 or 4 students.

2. Objectives

✔ To demonstrate practical knowledge of ‘Structured Software Engineering’ (Yourdon)

✔ To submit some basic Project Management Artifacts.

✔ To work successfully in a small group to a given time scale.

3. 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. Last project they suffer from significant issues such as no clear scope without no documentation outlining the specific features, integration points or end goals for the new system. Poor resource allocation drags on for months, leading to budget overruns and delays in other critical warehouse operations. Communication between the teams is sporadic and unstructured. There are no regular meetings or progress reports. Potential risks, such as system downtime not identified or mitigated on time. After the IMS is implemented, there is no review to assess whether the project objectives were met to identify areas for improvement. Due to the lack of project management, the implementation of the new IMS is deemed a failure. The warehouse continues to struggle with inefficiencies, financial losses and customer dissatisfaction, Eventually, the Global Tech corporation decides to strictly emphasize project management with proper analysis and design too for the upcoming year project.

4

3.1 Detailed specification of GROUP task

As a group task you are asked to produce a number of analysis and design specifications of a particular part of the system.

Each group member should select ONE of the following ‘functions’ for their individual task and clearly specify their name and their chosen functions clearly.

1. Access users to system:

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

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

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

4. Sales Management:

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

5

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

6. Payment:

While viewing the product, there should be a provision to compare prices between similar products in case customers want it. 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.

6

4. Your Tasks

Your main tasks are:

1. Prepare a Business Case (Note: While preparing a Business Case, you are free to make logical/sensible assumptions).

2. Specify and design substantial parts of the system using Structured approach (Yourdon).

4.1 Business Case

– Following proper template for business case provides clear, concise justification for project initiative, ensuring that it aligns with organizational goals and delivers values.

4.2 SRS

– Functional Requirements

– Non-Functional Requirements

– Design and Implementation Constraints

– External Interfaces Required

(User Interfaces, Hardware Interfaces, Software Interfaces,

Communication Interfaces)

– Other Non-Functional requirements.

4.3 Detailed specification of GROUP task

As a group you are asked to produce a number of analysis and design specifications of an overall system.

4.3.1 Environmental model specification

● Context Level, (DFD) Data Flow Diagram (level1, level2(for any 3 processes))

7

4.3.2 Internal model specification for the system.

● Entity Relationship Diagram (ERD)

● Data Dictionary (with definitions of major data flows and definitions of data stores and entities)

● Process specifications (Pspecs) for elementary processes.

4.3.3 Design specification

● Structure chart (upper level) for the whole system.

4.3.4 Progress Logs.

You are asked to produce to track overall progress of the project:

● All the assumptions you made,

● All the omissions/inconsistencies you have discovered in the provided specification.

● Group member responsibilities, group meeting minutes.

4.4 Detailed specification of INDIVIDUAL task

As an individual task you are asked to produce a number of analysis and design specifications of a particular part of the system.

Each group member should select ONE of the following ‘functions’ for their individual task and clearly specify their name and their chosen functions clearly.

1. Purchase Order

2. Report preparation

3. Real-Time Stock Updates

4. Dispatch Order

5. Payment

8

After selecting a function create the design specifications of the system as mentioned below:

Environmental model specification

● Context Level

Internal model specification for the system

● The Level 1 DFD fragments

● Level 2 DFDs for the particular function

Design specification

● Structure chart for the particular function.

● Module specifications (MSpecs) for corresponding modules

Please note that a template for MSpecs is given below under Footnotes.

5. Documentation

Each group should produce only ONE integrated copy of the report with the following structure:

Cover page – Coursework title plus names and London Met id numbers of the student. Contents page(s)

1. Introduction (a brief overview of the report)

2. Business case

3. SRS

4. Group tasks

a. Environmental model specification

b. Internal model specification

c. Design specification

d. Progress logs

5. Individual task

a. Environmental model specification

b. Internal model specification

c. Design specification

6. Summary (a brief summary of the report)

7. Reference

9

Foot-notes:

1 (Mspec) Component/module specification should have the following format:

MODULE NAME

PURPOSE. A brief description of the module’s function

PSEUDOCODE. Detailed description of the module’s function

INPUT PARAMETERS (if any)

OUTPUT PARAMETERS (if any)

GLOBAL VARIABLES (if any)

LOCAL VARIABLES (if any)

CALLS. References to other modules/components (including libraries). CALLED BY. Names of other modules/components using this one.

2. Presentation’s viva (VIVA by each group member during each milestones week and in the 11th week)

3. Plagiarism and / or collusion. Any evidence of plagiarism or collusion between groups and / or with entities outside the university may result in an investigation by the case work office and, if substantiated, one of a range of serious penalties may be applied to the student[s] concerned.

4. Marking Scheme

Group Marks	Marks
Business Case	7
SRS	10
Context Diagram	6
DFD	10
E-R Diagram	8
Data Dictionary	5
Process Specification	6
Structured Chart	6
Progress Logs	8

10

Individual Marks
Context Diagram	5
DFD	6
Structure Chart	6
Module Specification	10
Description	7

5. MILESTONES BREAKDOWN

MILESTONE	Tasks	Deadline
1	Project Artifacts – Business Case	Tuesday, 26 November 2024
2	SRS (Software Requirement Specification) Overall – Introduction Analysis artifacts – .DFD’s Both group and individual, E-R diagram.	Monday, 16 December 2024
3	Data Dictionary Overall Report – Progress Logs and Conclusion Diagrams – Structured Chart (Group and individual) – Module Specification(individual)	Tuesday, 24 December 2024

END

11