London Metropolitan University, Faculty of Computing

CS6003ES Advanced Software Engineering

Part 1 weighting: 30% in total

GROUP STUDENT ID NUMBERS: __________________________________

_____________________________________________________________________________

NAMES_____________________________________________________________________

_____________________________________________________________________________

Submission deadline: 30th July 2023

The hard copy and electronic version of your group report must indicate all group
members’ ID number, Surname and First name in the first page or at the beginning of
program file (as comments).

If you think there is a good reason for late submission, such as illness, and you have supporting documentary
evidence then you should follow the “mitigating circumstance” procedures outlined in the Red Book, otherwise
assignments will NOT be accepted by the module Organizer after the due date .

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:

(Signature:)_____________________________________________________________

_____________________________________________________________________________

This header sheet should be attached to the assignment specification and to the work you
submit. No work will be accepted without it.
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 unauthorized material into an examination; consulting
unauthorized material outside the examination hall during the examination; obtaining
an unseen examination paper in advance of the examination; copying from another
examinee; using an unauthorized calculator during the examination or storing
unauthorized 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 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 = mc2 (Einstein 1905)". A references
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.
 CS6003ES – Advanced Software Engineering COURSEWORK PART 1

SUBMISSION DEADLINE: 30th July 2023

1. Description and requirements:

You are required using an appropriate approach to analyse, design,

Scenario

A national railway corporation transports millions of passengers annually along several

General requirements for the system are as follows:

1. Ticket Booking: Passengers book tickets online, either through the company's website or
a mobile app. Passengers can search for available trains, choose their departure and
arrival times, select their preferred seating options, and pay for their tickets using a
secure payment gateway. The system automatically updates the inventory of available
seats and sends confirmation emails to passengers.
2. Train Tracking: Allows passengers to track the real-time status of trains, including their
departure and arrival times, locations, and delays (if any). Passengers can access this
information through the company's website or mobile app, which uses GPS and other
sensors to track the trains' movements. The system sends alerts to passengers if there are
any significant delays or changes to the train schedule.
3. Passenger Management: Manages the details of each passenger, including their personal
information, booking history, and loyalty program status. The system allows passengers
to create profiles, store their preferences, and earn rewards for frequent travel. The
system also provides customer support through various channels, including email, chat,
and phone.
Revenue Management: Manages the revenue generated by the company, including ticket
sales, promotions, and discounts. The system provides real-time data on revenue streams,
allowing company to make informed decisions about pricing, marketing, and other
business strategies. The system also generates reports on revenue and expenses, which
can be used for financial planning and forecasting.
By considering the brief outline requirement given above, the hidden and potential requirements are
to be derived by you for the purpose and mention those clearly. The hidden requirements are to be
logically match with the outline requirement given above.
Perform the following tasks individually and as a group to accomplish the application development,
Group Tasks:
 1. System architecture design with the communication Diagram.
2. Software requirements specification should clearly indicate the Potential requirements and
the hidden requirements (including required reports).
3. Software design and its specification using UML with Object Oriented Analysis Design
techniques.
4. The group is encouraged to use CASE tools for the development work and exhibit proper
understanding about the tools such as JIRA, GitHub etc.
Individual Tasks:
1. Each member of the group must implement a part (more than two components) of the
software, such as interface including login function, daily report software.
2. Each member of the group must test your implemented software. It includes software-testing
design (With Test cases), test implementation and test report. Encouraged to use automated
testing tools and test management tools.
This coursework also requires each group to give a group presentation in week 10. The requirements
for presentation have been included in the Marking Scheme.

2. Submission:
By the deadline you must submit an electronic version of the complete documentation and software.
3. Marking Scheme (TOTAL 100 MARKS):
The marks for this assessment are based on the following assessment criteria:

Items Max. Mark

Over all report including report title, 6%

Group presentation in week 10 20 %

Requirements specification 15 %
Functional, non-functional, user stories etc

Design specification 16 %
Use of UML diagrammatic techniques with OOAD
etc.

Implementation 20 %
Use any programming language/ Database / web
language of your choice. Use of CASE tools for the
implementation.

Testing 15 %
Software-testing design (With Test cases), test
implementation and test report., plus evidence of the
testing tools with prepared test data as specified in
the requirements specification

Total 100%

THIS COURSEWORK HAS TO BE COMPLETED IN GROUPS OF THREE TO FOUR