Scenario:

Three major universities that have campuses in Berlin, realize they have many

staff and students who have overlapping interests. There are many seminars

on interesting topics at each of the universities, but how does someone on one

campus find out about interesting seminars that are happening at one of the

other universities? The universities decide that they would like to create a Webbased academic talks listing service that will advertise talks and events to

researchers, students, postgraduates, and interested parties from outside

academia across Berlin.

But notes that a site suitable for academic interests across different campuses

will have some unique requirements. Although the system is open to the public

to sign up$,$ anyone claiming to have a university affiliation should be verified at

least by checking that they have a university email address.

Although anyone can create a talk or a series of regular talks in the system, it

is expected that most academic users will want to subscribe to the talk lists that

will be maintained by various interest groups. Administrators of an interest

Group

Assignment

CENTRE FOR POSTGRADUATE STUDIES

Prepared by Dr Mohammed Alimam

Advanced Software Design $2$

group should be able to manage which talks and which recurring talks should

be advertised as part of their list, remembering that sometimes they will only

be interested in one or two talks from a series and sometimes they will be

interested in the whole series. As the talks will be across many different

campuses, it$$s important that the location of a talk need to tell which campus

it is on$,$ and to be quickly able to access transport information $($generating links

that will use Translink$$s system and Google Maps to find out travel times from

the user$$s location$).$

The software requirement specification is merely for the software, but it needs

to include descriptions of the interfaces for any systems with which it needs to$.$

You may also consider various non$-$functional requirements for the system.

Tasks:

Develop a Software Requirements Specification document

$($Requirement Engineering$)$ to be prepared based on Specifications,

Requirement and tools for the development of a multi$-$campus, multi$-$field

academic talks listing service. This assignment is intended to be open$-$ended

and to provide you with an opportunity to demonstrate your creativity. As a

potential user of the website, you may wish to propose creative requirements

for the system by including the following:

$-$ List of Main functions and features

$-$ List of intended users mapped to specific functions based on the given

scenario

$-$ Data Flow diagrams and Entity$-$Relationship diagrams are used to

identify flow of data from one module to other. Design both diagrams,

$$ Part $1$: scope and domain of this task including explanation about main

scenario and sub$-$scenarios. Understanding and gathering

requirements, and the effectiveness of feasibility study to perform

CENTRE FOR POSTGRADUATE STUDIES

Prepared by Dr Mohammed Alimam

Advanced Software Design $3$

analysis and definition that leads to system architecture design,

graphical design and user interactions. And the way of selecting a test

plan for V&V as part of SDLC technique which results in standardizing

the level of QA based on development goals to identify

$1.$ System and software architecture

$2.$ LoQ

$3.$ CICD

$$ Design the UML to represent OOD based on the concluded SRS$.$

The previous part would represent processing of project backlog as an input

to be used in development phase.

$$ Part $2$: as a Planning part, Design of prototype of UI$,$ based on the

concluded sub$-$scenarios and diagrams, functionalities with mapping of

functional and non$-$functional requirements. Discuss how many

interfaces are to be proposed to reflect on the scenarios.

$$ API layer which execute business logic required in this case by

connecting it to UI$.$ Discuss the specification, requirements and tools

invoked

$$ Part $3$: create a functional checklist for quality testing to

validate output