LD7092 Principles of Software Engineering Assignment help

COURSEWORK ASSESSMENT SPECIFICATION

Dates and Mechanisms for Assessment Submission and Feedback                                                      

Learning Outcomes tested in this assessment

This assignment will assess the following learning outcomes: 
1.Demonstrate critical knowledge and understanding of appropriate software engineering theories, technologies and methodologies.
2.Ability to apply software engineering knowledge to a complex business challenge or project.
3.Critically reflect on professional, legal, social, security and ethical issues related to the design, development and use of software in an organisational context.
4.Ability to critically evaluate your Software Engineering skills.
5.Demonstrate problem solving skills in complex situations in the context of the design, development and use of software solution.

General Information
This assignment constitutes 100% towards the final mark for this module. Any queries relating to this assignment should be directed to module leader, ning.tse@northumbria.ac.uk

Type of the submission required.
This is an INDIVIDUAL piece of work divided into two tasks as follows.

1.    Practical Solution Prototype (50%)    Design and development of a program prototype solution using OOP language such as Java on the given case study. This activity assesses module learning outcomes 1, 2 & 5. (2000 words)
2.    Critical Discussion (50%)    Critical discussion of some issues relating to Software Engineering. This activity assesses module learning outcomes 3 & 4. (2000 words)

Case Study: Point-of-Sale (POS) System for Fashion Store 
Beauty Fashion (BF) is a casual wear retailer based in England.  As of May 2023, BF has opened 10 stores in the cities of London and Manchester.  There are around 100 employees working in the stores. BF has signed agreements with suppliers and manufactories in EU to provide various fashion products for their customers. In recent time, BF owner decided to develop a new Point-of-Sale system to manage the stores and serve their customers in an efficient way.

You are required to design and develop a user-friendly, desktop application to assist BF staff including cashiers, sales assistants and store managers in managing the inventory (clothes, accessories, footwear, etc.), answering customers’ enquiry on product variants and composites, managing transactions with customers, handling human resources and communicating with the other BF stores and suppliers.

The new system has to be designed in an appropriate way to enable the store staff to access the system and perform different activities such as: cashiers to collect payments and issue receipts, handle refunds; sales assistants to check the inventory records and collect fashion product for their customer; store manager to prepare sales records, run promotion, order fashion products and manage staff including cashiers and sales assistants.

The system should allow registered users to use it only after login. Key features of the BF point-of-sale system include:

-User friendly GUI based system for staff to use in the stores
-Receipt printing, payment collection, refund handling
-Generate notification detailing items that are low or out of stock
-Inventory record management
-Human resources management
-Sales records generation and analysis
-Any other relevant services

Task 1: Design and Development (50%, Learning Outcome 1 & 2 & 5)

Using the provided case study, develop a solution from a system analyst’s perspective that includes the following:

Produce a Use Case Diagram to model the functional requirements from the scenario narrative.
Showing actors and the use cases they perform.
Use inheritance where necessary of both use cases and actors.
Use of <<includes>> and <<extends>> where necessary.
Use house style model to document at least two primary use cases.

Produce a Class Diagram to model the system structure for your potential solution. This should include:

Detailed classes with all key variables/attributes and datatypes with access modifiers (private, public or protected) clearly shown in adherence to encapsulation principle of OOP.
Procedures or functions with (parameters and their datatypes shown) as well as return type for the class functions. (see diagram example below)
Use of class relationships (e.g. dependency association, aggregation, composition and inheritance).
An example of class diagram for product ordering system 

Produce a Sequence Diagram to model functional requirements from the scenario narrative for two key primary use cases. Decouple as much as possible with Boundary, Control and Entity.

Showing actors and interacting objects.
Messages (Methods) calls between objects with parameters and return types were necessary.
Use of alternatives and loops where necessary.
An example of sequence diagram is shown in Figure 2.

Develop the Interfaces using OOP language (Java with NetBeans IDE)
Document your solution with relevant screenshots and snippets of codes.
Produce a test plan and test cases.

NOTE: The solution is only going to be a prototype of the software architect level, but a skeletal code should be produced. You do not need to write any advanced level functionality into the methods or permanent data storage, but you must build and design the Forms (eg, JFrames and JPanels) and link them to each other with relevant GUI components such as buttons, text fields, labels etc. The program should be executable (i.e. no compile time errors that prevent it from being executed).

Task 2: Reflection and Critical Evaluation (50%, Learning Outcome 3 & 4)

You are required to write a report to address the following topics:

•Using software engineering literature, critically evaluate the Software Development Life Cycle (SDLC) methodology you have chosen for your solution development with relevant examples from your work (clarify how you applied it in the various SDLC phases).
•Critically reflect on professional, legal, social, security and ethical issues related to the design and development of your solution.

This is meant to be a critical discussion and not just a description. Your discussion should not be limited to your practical system (the prototype), but a discussion of the broader issues involved in the design of your solution such as the functional requirements, use case documentation, the main classes involved in the class diagram and sequence diagram with justification of any important design decisions.

Format and Submission Requirements
Submission will be via Turnitin on Blackboard; please see the front cover for the submission date. You can submit your report for originality checking via the ‘Draft Submission Point’.  However, you must ensure the final version is correctly submitted to the ‘Final Submission Point’ before the deadline.

Combine all tasks into one single MS Word document.  Your discussion for the practical solution commentary should contain 2000 words and for the reflection and critical evaluation 2000 words. 

Add a cover page with your name, student ID, tutor’s name and word counts for each task. 

Include table of contents, page numbers, captions for all figures and tables.  Layout should make reasonable use of margins, numbered headings, 1.2~1.3 line spacing, Times New Roman font style and 12pt font size.  

Referencing should be in the Harvard or APA style. If you require guidance on citation, please use the booklet ‘Cite Them Right’ available from the City Campus library. The online Northumbria Library is also a good source of references at this academic level as the Library subscribes to the leading information sources in Computing. Since Computer Science is highly dynamic, recent references to conference and journal papers from the last five years are preferred. 

Name your report with tutor’s name, programme code, group no and your student ID: LD7092_<tutor_initial>_<prog code & intake>_<student ID>.docx.  Eg, LD7092_NT_CT_
w22012345.docx for a Computing & Technology student, attending Ning Tse’s class.

Project directory should also be submitted in one single zip file with same filename format, ie LD7092_<tutor_initial>_<prog code & intake>_<student ID>.zip. Simply submitting individual .java files will receive a mark of Zero for the program section.  Use meaningful naming conventions for variables, methods and classes.

Assessment Criteria/Marking Scheme:

Formative Feedback: There will be an opportunity for formative feedback during the semester. You are advised to start working on this assignment as early as possible so that you can seek clarification from the module tutor regarding any questions you might have during the semester. Note that tutors will not predict your grade, and you should not take the lack of comment on any aspect of your work as indicating that it is correct. You should make every effort to take advantage of formative feedback as tutors will not comment on draft work at other times. Remember that you will get more useful feedback from us by asking specific questions than just presenting us with your documentation and asking, ‘Is this right?’

Academic Integrity Statement: You must adhere to the university regulations on academic conduct. Formal inquiry proceedings will be instigated if there is any suspicion of plagiarism or any other form of misconduct in your work. Refer to the University’s Assessment Regulations for Northumbria Awards if you are unclear as to the meaning of these terms. The latest copy is available on the University website here.

Penalties for Exceeding Word Limits: The actual word count is to be declared on the front of the assessment submission. 

Late Submission Policy: For coursework submitted up to 1 calendar day (24 hours) after the published hand-in deadline without approval, 10% of the total marks available for the assessment shall be deducted from the assessment mark. Penalties will be applied as defined in the University Policy on the late submission work. The latest copy is available on the University website here.

For clarity: 1 calendar day counts from 16:01 of 28th to 16:00 of 29th, December 2024.  A late piece of work that would have scored 65%, 55% or 45% had it been handed in on time will be awarded 55%, 45% or 35% respectively as 10% of the total available marks will have been deducted.

Failure to Submit: The University requires all students to submit assessed coursework by the deadline stated in the assessment brief.  Where coursework is submitted without approval after the published hand-in deadline, penalties will be applied as defined in the University Policy on the Late Submission of Work.

Module Specific Assessment Criteria