✍️ Get Writing Help
WhatsApp

Principles of Software Engineering

COURSEWORK ASSESSMENT SPECIFICATION
Module Title:Principles of Software Engineering
Module Number:LD7092
Module Tutor Name(s):Hassan Baajour
Academic Year:2020/2021
% Weighting (to overall module):100%
Coursework Title:Assignment
Average Study Time Required by Student60-70 hours to complete assignment
Dates and Mechanisms for Assessment Submission and Feedback
Date of Handout to Students: During Week 1 of teaching
Mechanism for Handout to Students: Blackboard
Date and Time of Submission by Student:
11 Jan 2020 at 16:00
Part A: Component 1: Software design and project prototype Part B: Component 2: Critical-Evaluation
Mechanism for Submission of Work by Student: The reports must be submitted via Turnitin. The source code MUST be attached to the report.
Date by which Work, Feedback and Marks will be returned to Students: Within 20 working days after submission of this assignment
Mechanism for return of assignment work, feedback and marks to students: Formalfeedbackwilltakeplace followingcompletionofallreviewsand internal moderationofresults.

Learning Outcomes Tested in this assessment:

The following learning outcomes will be assessed by this assignment:

  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.

Assignment Overview:

The assignment is divided into two components as follows:

Practical Solution Prototype (50%)Individual Work– design and development of a program prototypesolution using Java based on the case study given below. This activity assesses module learning outcomes 1, 2 & 5. (2000 words)
Critical Discussion (50%)
Individual work – critical discussion of some issues relating to Software engineering. This activity assesses module learning outcome 3 & 4. (2000 words)

General description

Case Study: Durham College E-Learning Platform (DELP)

Durham college is a private school that provides a wide range of academic courses leading to internationally recognised qualifications in computing, business, travel & tourism management, hospitality management and healthcare.

The new director of Durham college has decided to move all of its teaching activities from their campus in the city into online learning platform in order to protect its students and staff from COVID‑19, which is an infectious disease that has resulted in an ongoing pandemic across the world.

Durham college ELP would be offering a complete learning experience that is rich with learning resources, fun, interactive, and ultimately engaging. Durham new ELP will provide a comprehensive integrated set of interactive online services that offer admins, tutors, learners, and others involved in education at Durham college with information, tools and resources to support and enhance students enrolment, education delivery, assessment and financial management.

The new ELP should be an innovative online learning management system (LMS) that allows Durham college staff to manage online courses including create, update, search, delete courses and assessment. The LMS should offer an interface to enable students to interact with the learning resources easily including finding and view learning content, complete tutorials and tasks, submit assignments via Turnitin and check their results. The system should offer parents the possibility to monitor their children progress and to communicate with the tutors. Admin team will be able to manage time tables, enrol students into courses and arrange staff-parents meetings. In addition they will be able to view if students fees payments are up to date via Sage service integrated with the MLS. Sage has been chose as it is a leading provider of enterprise resource planning software, which offer comprehensive accounting services, customer relationship management, inventory management and much more.

Simply, the purpose of the new e-learning platform for Durham college is that it creates a robust learning experience that feels like a classroom experience, offering the traditional classroom characteristics (like instructor-student interaction, Q&As, discussion, collaborative projects, quizzes, etc.), all of which will be running and managed online.

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 one primary use case.
  • Produce a class diagram to model the system structure you propose for your potential solution. Decouple as much as possible with Boundary, Control and Entity classes. 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 principal 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 a basic class diagram



  • Produce a sequence diagram to model functional requirements from the scenario narrative for one primary use case.
    • 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 detailed sequence diagram

Program:

  • Develop the proposed solution using OOP language (Java with NetBeans IDE). 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 advanced level functionality into the methods or permanent data storage but you must build and design the Forms (JFrames) and link them to each other with relevant GUI components such as buttons, text fields, labels etc.

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

You are required to write a reportthat contains a critical discussion, reflection and evaluation. Name your report using your user ID, e.g. w1612345report.

Given that, please address the following topics in your discussion:

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

Your discussion for the practical solution commentary should contain 2000 words and for the critical evaluation 2000 words and should be presented in the form of a word document and submitted to eLP Blackboard.

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.

References

References must be used in order to strengthen any points that you raise in your discussion.

Your discussion must be your own words and, where you have used someone else’s words (quotations), they should be correctly quoted and referenced in accordance to the Harvard or APA System. If you require guidance on citation, please use the booklet ‘Cite Them Right’ available from the City Campus library.

The online Northumbria Library is 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.

References are not included in the word count.

Additional Programming Requirements:

Your code must comply with the following requirements:

  • OOP language – Java should be used as the programming language.
  • Use NetBeans IDE
  • The program should be executable (i.e. no compile time errors that prevent it from being executed).
  • Project directory should be attached to your word document with the commentary in a zip file. Simply submitting individual .java files will receive a mark of Zero for the program section.
  • Use meaningful naming conventions for variables, methods and classes.

Marking Scheme

The following marking scheme will be used for this assignment:

DescriptionMarks

Practical Solution (50%)

Use case modelling List of functional requirements Logical design showing actors and associations including inheritance (generalisation/specialisation) of actors and use cases as appropriate. Comprehensive use case documentation using house style.10
Class diagram: Logical design showing classes and members (functions and procedures with parameters and return types) Efficient design using object oriented features such as encapsulation, abstraction, inheritance, polymorphism and composition/aggregation where applicable. Use of design patterns e.g. MVC. Documentation of main classes and associations.10
Sequence diagram: A logical design showing all objects involved in the use case scenario. Messages/Method calls that reflects class diagram structure and communications. Parameters and return types shown. Control structure using alternatives and loops.10
Program: A working prototype which reflects the class diagram designs. Use of coding standards, comments. Use of OOP principles (e.g. abstraction, inheritance, encapsulation, polymorphism where applicable).20

Critical Discussion (50%)

Critical evaluation of SDLC and justification of chosen methodology in context of your solution.20
Critically reflect on professional, ethical and security issues related to the design, development and use of software in the given project context.
20
Citations, references and report structure10

Total Marks Available: 100

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.

https://northumbria-cdn.azureedge.net/-/media/corporate-website/new-sitecore-gallery/services/academic-registry/documents/qte/assessment/guidance-for-students/pl,-d-,005-v004-academic-misconduct-policy.pdf?la=en&modified=20200117152110&hash=5631FCFB09A073D1BEE7BD157FAB19313A10268A#:~:text=1%20Academic%20Integrity,-1.1%20Every%20student&text=1.2%20In%20all%20assessed%20work,advantage%20in%20any%20other%20way.

(last accessed on 25th August 2020)

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?’

Penalties for Exceeding Word Limits:


The following penalties will be applied after any reductions in mark due to late submission have been made, Penalties will be applied as defined in the University Policy on Word Limits Policy.

https://northumbria-cdn.azureedge.net/-/media/corporate-website/new-sitecore-gallery/services/academic-registry/documents/qte/assessment/guidance-for-students/pl013-v002-word-limits-policy.pdf?modified=20200803200335.

(last accessed on 25th August 2020)

The actual word count is to be declared on the front of the assessment submission.

Late Submission Policy:

For coursework submitted up to 1 working day (24 hours) after the published hand-in deadline without approval, 10% of the total marks available for the assessment (i.e.100%) shall be deducted from the assessment mark. Penalties will be applied as defined in the University Policy on the Late submission work.

https://northumbria-cdn.azureedge.net/-/media/corporate-website/new-sitecore-gallery/services/academic-registry/documents/qte/assessment/guidance-for-students/pl,-d-,008-v004-late-submission-of-work-and-extension-requests-policy.pdf?modified=20200803152930

(last accessed on 25th August 2020)

For clarity: 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.

https://northumbria-cdn.azureedge.net/-/media/corporate-website/new-sitecore-gallery/services/academic-registry/documents/qte/assessment/guidance-for-students/pl,-d-,008-v004-late-submission-of-work-and-extension-requests-policy.pdf?modified=20200803152930

(last accessed on 25th August 2020)

Module Specific Assessment Criteria

Please see attached rubric

Criteria


Scales



0-39%40-49%50-59%60-69%70-79%80-89%90-100%

Standard Not MetStandard Not MetMeets Standard 1Meets Standard 2Standard 3ExceedsExceeds Standard






Standard 23
Use case model [10%]





Clearly insufficient; Student is not able to demonstrate logical design. Actors or use cases are not available.






Insufficient; Student is not able to demonstrate logical design. Actors, use cases and associations are less than the expected minimum.





Student is able to demonstrate logical design. Key actors, use cases and associations are modelled in a way that meets the fundamental requirements.



Student is able to demonstrate logical design. Actors, use cases and associations includes all primary actors and functions. In addition to the use of inheritance and good design of use case documentation using house style.

Logical design meets standard 2 plus very good use of inheritance, includes and extends.







Logical design meets standard 3 plus excellent use of inheritance, includes and extends. Clearly exceeds taught material.





Student is able to demonstrate outstanding logical design. All actors, use cases and associations ( primary use cases, some secondary use cases). In addition to excellent use of inheritance, includes and extends with no errors or mistakes. Clearly exceeds taught material.
Outcome[0-3][4][5][6][7][8][9-10]
Class Diagram [10%]





Clearly insufficient; Student is not able to demonstrate logical design. Essential classes are not available.









Insufficient; Student is not able to demonstrate logical design. Essential classes are available however, no (or very bad) properties, operations and associations.






Student is able to demonstrate logical class diagram modelling. Main classes, properties and associations are modelled in a way that meets main requirements.






Student meets standard 1 plus good. Use of multiplicities, inheritance, and encapsulation.










Student meets standard 2 plus very good use of multiplicities, inheritance, encapsulation, composition and aggregation.







Student meets standard 3 plus excellent use of multiplicities, inheritance, encapsulation, composition and aggregation. Clearly exceeds taught material.





Student meets standard 3 plus innovative modelling demonstrated, with excellent use of multiplicities, inheritance, encapsulation, composition and aggregation with no errors or mistakes. Clearly exceeds taught material.


Outcome[0-3][4][5][6][7][8][9-10]
Sequence Diagram [10%]





Clearly insufficient Key lifelines / objects missing, no or very bad messages communication






Insufficient Key lifelines / objects available, bad messages communication





Key lifeline / objects available, with adequate messages communication





Major lifeline / objects available, with satisfactory sequence of messages communication




Major lifeline / objects available, with very good sequence of messages communication plus good control structure






All lifeline / objects available, with excellent and detailed sequence of messages communication plus excellent control structure. Clearly exceeds taught material.







All lifeline / objects available, with outstanding and detailed sequence of messages communication plus excellent control structure with no errors or mistakes. Clearly exceeds taught material.
Outcome[0-3][4][5][6][7][8][9-10]
Critical evaluation of SDLC and justification of chosen methodology in context of your solution [20%]











Clearly insufficient; Basic description of SDLC, without critical evaluation of SDLC Methodologies



















Insufficient; Basic description of SDLC, and Methodologies. However, no critical evaluation or justification of chosen methodology in context of the given solution
















Adequate description of SDLC, and Methodologies with satisfactory evaluation and justification of chosen methodology in context of the given solution. Adequate citation and references to support ideas and arguments.














Satisfactory evaluation of SDLC, and Methodologies with critical reflection and justification of chosen methodology in context of the given solution. Satisfactory citation and references to support ideas and arguments.














Critical evaluation of SDLC, and Methodologies with critical reflection and justification of chosen methodology in context of the given solution with proper and relevant examples. Good citation and references to support ideas and arguments.










Critical evaluation of SDLC, and Methodologies with critical reflection and justification of chosen methodology based on a comparisons by other methodologies including advantages and disadvantages in context of the given solution with proper and relevant examples. Very good citation and references to support ideas and arguments. Clearly exceeds taught material.







Outstanding reflection and critical evaluation of SDLC, and Methodologies with critical reflection and justification of chosen methodology based on a comparison with other methodologies including advantages and disadvantages in context of the given solution with proper and relevant examples. Excellent citation and references to support ideas and arguments. Clearly exceeds taught material.









Outcome[0-5][6-9][10-11][12-14][15-16][17-18][19-20]
professional, ethical and security issues [20%]





Clearly insufficient; Only basic description of professional, ethical and security issues.






Insufficient; Adequate description of professional, ethical and security issues without relating it to the design, development and use of software in an organisational context




Satisfactory description of professional, ethical and security issues with relevant examples related to the system design, development and use in the given context. Adequate citation and references to support ideas and arguments.
Good evaluation of professional, ethical and security issues with good examples related to the system design, development and use in the given context. Satisfactory citation and references to support ideas and arguments.Critical evaluation and reflection on professional, ethical and security issues with very good examples related to the system design, development and use in the given context. Good citation and references to support ideas and arguments.Critical evaluation and reflection on professional, ethical and security issues with excellent examples related to the system design, development and use in the given context. Very good citation and references to support ideas and arguments. Clearly exceeds taught material.Critical evaluation and reflection on professional, ethical and security issues with excellent discussion and examples related to the system design, development and use in the given context. Excellent citation and references to support ideas and arguments. Clearly exceeds taught material.
Outcome[0-5][6-9][10-11][12-14][15-16][17-18][19-20]
Citations and references and report structure [10%]





No or very insufficient citations and references, with bad report structure











Insufficient citations and references, with inadequate report structure










Adequate citations , references and report structure












Satisfactory citations , references and report structure












Very Good citations, references and report structure












Excellent citations , references and report structure












Outstanding citations , references and report structure.












Outcome[0-3][4][5][6][7][8][9-10]
Overall Mark


[–/100 ]
















Further Comments:



















For faster services, inquiry about  new assignments submission or  follow ups on your assignments please text us/call us on +1 (251) 265-5102