Assignment Brief 2022
Assignment Brief 2022
Department of Computing
COMP4002 Object Oriented Analysis and Design with UML (EFREI)
Learning Outcomes
1. Employ an object-oriented approach to design and implement software systems.
2. Apply a suitable notation to model solutions to problems
3. Create OO design systems from analysis requirements architecture and UML models
Assignment – 1 Worth 20% of module marks (Display in Class – Upload via Blackboard)
Assignment – 2 Worth 30% of module marks Handin (Class Presentation Group Slots)
The University Regulations regarding extenuating circumstances and plagiarism will apply.
Standard submission rules apply. Late submissions attract ZERO marks.
Marking grids are shown at the end of this document.
All submissions are handed in electronically via Blackboard at the time specified below. Presentations in groups. Timeslots given for each group.
Task One –Individual assignment.
Create: Use Case, Class, Activity, and Sequence -UML Diagrams from the Scenario below.
Task Two – In Small Groups. Research, Analyse, Document and then Produce a Group Presentation lasting 15 minutes each group. On the Scenario below. Using Object Oriented Analysis, Systems Requirements Theory, along with FURBS+.
Scenario-1
A Library Management System is a software built to handle the primary housekeeping functions of a library. Libraries rely on library management systems to manage asset collections as well as relationships with their members. Library management systems help libraries keep track of the books and their checkouts, as well as members’ subscriptions and profiles.
Library management systems also involve maintaining the database for entering new books and recording books that have been borrowed with their respective due dates.
Scenario-2
Online Shopping System
Analyse the system requirements that would develop an online retail store.
Businesses like Amazon (amazon.com) is the world’s largest online retailer. The company was originally a bookseller but has expanded to sell a wide variety of consumer goods and digital media. For the sake of this problem, we will focus on their online retail business where users can sell/buy their products.
Task One – Create UML Diagrams (20%)
Create UML Diagrams: For Example: Use Case, Class, Activity, and Sequence - diagrams for a Library Management System: These diagrams to be detailed. The system should at least include:
1. Any library member should be able to search books by their title, author, subject category as well by the publication date.
2. Each book will have a unique identification number and other details including a rack number which will help to physically locate the book.
3. There could be more than one copy of a book, and library members should be able to check-out and reserve any copy. We will call each copy of a book, a book item.
4. The system should be able to retrieve information like who took a particular book or what are the books checked-out by a specific library member.
5. There should be a maximum limit (5) on how many books a member can check-out.
6. There should be a maximum limit (10) on how many days a member can keep a book.
7. The system should be able to collect fines for books returned after the due date.
8. Members should be able to reserve books that are not currently available.
9. The system should be able to send notifications whenever the reserved books become available, as well as when the book is not returned within the due date.
10.Each book and member card will have a unique barcode. The system will be able to read barcodes from books and members’ library cards.
Task Two - Research, Analyse, and Document a Group Presentation (30%)
1. In Small Groups. Research, Analyse, Document and then Produce a Group Presentation lasting 15 minutes each group
3. Functions and features, business information systems are identified as enterprise computing systems, transaction processing systems, business support systems, knowledge management systems, user productivity systems, digital assistants, or systems integration.
4. Popular , which include the latest trends in software development.
5. How could an Online shopping store benefit from these approaches?
6. Produce documents mind maps and charts and diagrams to enhance your presentation et cetera.
7. In the Presentation all members are required to present at least one topic.
8. Use all the background reading you have done on Systems requirements analysis.
9. Design functional requirements specification to present and overall detailed structure of the positive benefits of using detailed requirement documentation and analysis.
10. Use any appropriate media and presentation method to perform the 15-minute presentation.
11. At the end of the presentation prepare for Q&A.
Task One Marking Grid
Table 1
Column 1
Column 2
Column 3
Column 4
Column 5
Column 6
1
Area
Fail
(0-49%)
Adequate
(50-59%)
Good
(60-69%)
Excellent
(above 70%)
20
2
•Use Case Diagram: How well does it describe a set of user scenarios,
Does the diagram, illustrates the functionality provided by the system.
Not enough structured set of scenarios that illustrate functionality with little accuracy but not enough details and depth.
Some structured set of scenarios that illustrate functionality with some accuracy but not enough details and depth.
Well-structured set of scenarios that illustrate functionality with some appropriate accuracy.
Thoughtful, consistent set of scenarios that illustrate functionality with precise accuracy.
5
3
•Class Diagram: How much detail has been used to describe structure and behaviour in the use cases, does this diagram provides a conceptual model of the system in terms of entities and their relationships
Limited and weak choices but no functions. with little conceptual models and relationships.
Basic, some weak choices but functions. with basic conceptual models and relationships.
Good choices of detail and descriptions in diagram along with good conceptual models and relationships.
Advanced detail and descriptions in diagram along with excellent conceptual models and relationships
5
4
•Activity Diagram: How well does this model the functional flow-of-control between two or more class objects.
Diagrams hard to interpret or inadequate for the job.
Basic diagram and sketches and average use of tools and functional flow of control. Not enough detail.
Clear and legible layout and diagrams. In functional flow-of-control
High production values in the diagramming; good use of tools. In functional flow-of-control between two or more class objects.
5
5
•Sequence Diagram: How Accurate is this to describe interactions among classes in terms of an exchange of messages over time
Limited and weak choices in interactions among classes in terms of an exchange of messages over time with little
Basic diagram and average use of tools and to describe interactions among classes in terms of an exchange of messages over time
Good choices of detail and descriptions in diagram along with good conceptual models’ interactions among classes in terms of an exchange of messages over time.
Advanced detail and descriptions in diagram along with excellent interactions among classes in terms of an exchange of messages over time
5
There are no rows in this table
Task Two Marking Grid
Table 2
Column 1
Column 2
Column 3
Column 4
Column 5
Column 6
1
Area
Fail
(0-49%)
Adequate
(50-59%)
Good
(60-69%)
Excellent
(above 70%)
30
2
How much did this group use: Object Oriented Analysis, Systems Requirements Theory, along with FURBS+
Not enough knowledge in most areas and did not meet the minimum elements
Some but not full areas covered of theory and needed more details in parts
Mostly functioning knowledge of theory and requirements.
Complete, working knowledge of subject matter.
10
3
Presentation of system development approaches are structured analysis, methods, object-oriented analysis and agile methods
Weak and limited structured analysis, methods, object-oriented analysis, and agile methods
Adequate structured analysis, methods, object-oriented analysis, and agile methods
Good structure and detailed approaches in analysis and methodologies.
Excellent and detailed approaches in analysis and methodologies.
10
4
Discretionary Marks on Development Documentation – Presentation Style and detail of Insight and knowledge
Incomplete or missing presentation, with poor quality, difficult to understand and display of limited knowledge.
Basic and Adequate in presentation with some useful parts of knowledge systems.
Well-presented information with enough detail to be useful
Professionally presented and complete Excellent knowledge base and insight thoughtful in structure and approach.
10
There are no rows in this table
Task Three Marking Grid
Table 3
Column 1
Column 2
Column 3
Column 4
Column 5
Column 6
1
Area
Fail
(0-49%)
Okay
(50-59%)
Good
(60-69%)
Excellent
(above 70%)
30
2
Tests: Pages work as they should
Broad and generic “tests” which are not very specific.
Lacking validation.
Most fields tested for basic input and output.
Most navigation tested. Validation tests documented.
All tables and fields tested with a good range of inputs.
Navigation fully exercised. Validation tests documented.
Tables, fields, navigation and extras thoughtfully tested. Validation tests documented and commented on.
10
3
Tests: Pages are styled correctly
Weak testing of styling and colour, poorly documented. Lacking validation.
Most styling and layout is checked and documented.
Validation tests documented.
All styling, layout and colours checked. Validation tests documented.
All styling, layout, colours and extras thoughtfully tested. Validation tests documented and commented on.
10
4
Reflection – what did you learn? Personal, technical and social skills.
Missing or irrelevant comments.
Some discussion of skills and techniques used.
Good discussion of learned skills, techniques and opportunities.
Thoughtful and balanced discussion of skills and techniques learned, opportunities taken.
10
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.