SCHOOL OF COMPUTER SCIENCES

ACADEMIC SESSION: 2023/2024

CSE241/CMM341 FOUNDATIONS OF SOFTWARE ENGINEERING
Software Engineering Project

Project Report 2

Project Report 2 covers four main elements of the software engineering project:

A. Project Background & Requirements

The project background describes the problem which the project seeks to address or
it is an opportunity that will lead to a great innovation. It justifies why this project is
important and why the project sponsors or clients should support it. It provides an
overview of the proposed system, system description and functionality together with
project team structure and roles.
The project requirement section describes both the functional and non-functional
requirements of the system.

B. Project Management & Planning

The purpose of this section is to give you an appreciation of managing software
projects. Once a project is planned, it needs to be managed because professional
software engineering is always subject to organizational budget and schedule
constraints. The project plan which is created at the start of a project and updated as
the project progresses, is used to show how the work in a project will be organized
as separate tasks, and when and how these tasks will be executed.

C. System Architecture and Design

Architecture and design are concerned with understanding how a software system
should be organized and designing the overall structure of that system. It is the

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)

critical link between design and requirements engineering, as it identifies the main
structural components in a system and the relationships between them. The level of
detail in the design depends on the type of system being developed and whether you
are using a plan-driven or agile approach. In agile, you should develop architectural
and design models that are useful for communication.

D. Software Quality & Testing

The purpose of this section is to give you an appreciation of designing black-box test
cases where tests are only derived from the system requirements specifications. The
software solution is treated as a black box whose behavior can only be determined
by studying its inputs and the related outputs. Another name for this is functional
testing, so-called because the tester is only concerned with functionality and not the
implementation of the software.

Tasks
Prepare a project report (1000 – 1500 words) with the following sections and
subsections in sequence:

Cover page
- Table of contents
- List of figures
- List of tables

1. Project Background & Requirements

1.1 Problem Background and Organization Background
1.2 System Overview
1.2.1 System Objectives
1.2.2 System Module Breakdown
1.3 System Requirements
1.3.1 Functional Requirement Analysis – Use Case Diagram
1.3.2 Non-Functional Analysis
Note: You can revise any diagram from REPORT 1, using any open-source tools for this
purpose and provide snapshots of the diagram in this section.

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)

2. Project Management & Planning
2.1 Project risk and feasibility
Construct a risk analysis table which covers the organizational, technological,
resource and schedule risks. You may use the table template below.
Risk description Type of risk Risk probability Proposed
solution / strategy
Give short text Organizational/ Low / medium / high Propose the way
description about technological / (give your how you can
the risk resource / schedule description of range) mitigate / minimize
the risk

2.2 Project iteration schedule

Assuming that your team is using Agile development methodology. Show the list of
iterations/sprint and use cases assigned to each iteration by using the template
below.
Iteration/sprint Time Estimate Use case assigned to iteration
1 X week 1. Xxxx
2. Yyy
3. zzzz
2
3
4

2.3 Work breakdown structure (WBS)

Show the hierarchy of activities and tasks used to estimate the work to be done in a
project (for all iterations).

2.4 Gantt Chart

Derive an overall Gantt chart for your full project development process.

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)

3. System Architecture and Design
3.1 Architectural design – Class Diagram
- Draw a class diagram which shows the relevant classes and attributes to be
used in the system. Show necessary relationships in the class diagram. Briefly
describe the diagram in 1-2 paragraphs.
3.2 Detailed design (Prototype)
3.2.1 Prototype tool: describe the tool used to implement the prototype.
3.2.2 Provide sketches of your system designs with high-fidelity UI by using
appropriate design software and briefly describe your UI. Suggest
presenting the UI by each module, using the storyboard method.

4. Software Quality & Testing

4. 1 Test Cases
Provide a suite of test cases to test the features in a table form as shown below.
Make sure that your tests covered all the uses cases in each module.
Test Case ID <<this field uniquely identifies a test case
identifier>>

Use case ID <<this field uniquely identifies a use case

identifier>>

Use case name <<this field uniquely identifies a system

feature (use case)>>

Test Input Expected Result Pass Criteria Fail Criteria

<<The input data <<The behavior <<Decision rules <<Decision rules

received from an predicted by the used to determine used to determine
external source by specification, or whether a test item whether a test item
the test object during another source, of (function) or feature (function) or feature
test execution. The the component or has passed test>> has failed a test>>
external source can system under
be hardware, specified
software or conditions>>
human>>

- References (at least 5 references with suitable referencing style – Harvard /

APA / IEEE)
- Appendices (if any)
- Assessment Rubric

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)

Cover page:
- Provide your team’s name, SDG that you are addressing, project title, project
member names, matric numbers, schools and project roles, as shown in the
table below.
- State submission date on the cover page of the report.

Team name: ABC

SDG XX: <<SDG in full text>>

Project title: <<title name>>

Student Name Matrix Number School Project Role

Submission date:
22 January 2024 (Week 15) / Monday

Submission method:
1 PDF report, via eLearn page

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)

 Assessment Rubric
Criteria A, A – B+, B, B- C+, C, C- D+, D, D-, F Given Marks
Superior Command Good Command Fair/Some Command Poor or No Command
Project Presented a very good introduction Presented a good introduction of Presented a fair introduction of the Presented a poor introduction of
Background of the domain and proposed the domain and proposed system. domain and proposed system. Key the domain and proposed system.
(10%) system with key aspects Some key aspects were aspects were not well highlighted. Key aspects were not highlighted.
highlighted. highlighted. Fair system and project planning. Poor system and project planning.
Excellent system and project planning. Good system and project planning.

Requirements Functional requirement analysis Functional requirement analysis Functional requirement analysis Functional requirement analysis
(10%) was sufficient and very well was sufficient and well presented. was fair and well presented. Use was poor and not well presented.
presented. Use case diagram was Use case diagram was presented case diagram was not presented Use case diagram presented badly
presented well with the help of fairly (with minor error) with the well (with major error) with the help (entirely wrong) even with the help
digital tool. help of digital tool. of digital tool. of digital tool.
Non-requirement analysis was Non-requirement analysis was Non-requirement analysis was Non-requirement analysis was
provided accurately. provided with minor error. provided with major error (not totally wrong.
relevant requirements are given).
Project Presented a very good project Presented good project Presented a fair project Presented poor project
management management and planning. management and planning. Some management and planning. Details management and planning. Details
and planning Details were presented. The details were presented. The charts were not well presented. The charts were not presented. The charts and
(25%) charts and diagrams were and diagrams were illustrated with and diagrams were illustrated with diagrams were illustrated wrongly,
illustrated accurately. minor errors. major errors. or totally incorrect contents/format.
System Presented a very good system Presented a good system design. Presented a fair system design. Presented a poor system design.
Architecture design. Details were presented. Some details were presented. The Details were not well presented. Details were not presented. The
and Design The charts and class diagram charts and class diagram and The charts and class diagram and charts and class diagram and
(25%) and prototype UI design were prototype UI design were illustrated prototype UI design were illustrated prototype UI design were illustrated
illustrated accurately. with minor errors. with major errors. wrongly, or totally incorrect
contents/format.

Software Quality Test cases were sufficient and very Test cases were sufficient and well Test cases were fair and well Test cases were poor and not well
& Testing well presented. presented. presented. presented.
(20%)
Organization - Report is well organized, easy to Report shows adequate Report is poorly organized, difficult Report has no organization, not
Neatness & read, and very neat. organization, readable, and neat. to read, and somewhat messy. easy to read, and messy.
completeness All report sections were covered There was minor incomplete There was major incomplete Almost all sections were missing in
(10%) fully. section in the report. section in the report. the report.
Total Score

Written comments:

CSE241/CMM341 FOUNDATIONS OF SE: SESSION 2023/2024 (AMK & LCY)