Reference no: EM132845563

COMP1471 Enterprise Software Engineering Development - University of Greenwich

Learning Outcome 1: Understand and reflect on the problems which are addressed by modern software engineering methods.

Learning Outcome 2: Acquire a theoretical and practical knowledge of component based software design and development and evaluate and select appropriate software design tools and techniques to assist the development of component based distributed computing systems.

Learning Outcome 3: Critically evaluate the quality of software design and architecture and apply modern modelling techniques and methods to the whole life cycle of real enterprise software systems.

The Case Study:

You have been approached by a construction company called Straight Walls Ltd to develop a holiday booking system. The company gives all of its employees a number of days of holiday entitlement per year. In the last few years the number of employees increased to almost 200 and the company has found it difficult to continue functioning properly at times when staff are on leave. The company relies on a variety of skills in their daily operations. This is aggravated by the fact that staff often go on leave at similar times of the year and the company is wondering how it can ensure that it can still operate well at these times.

To address this problem the company has asked for an automated holiday booking system which can capture constraints such as:
• Holiday entitlement
• Minimum number of staff levels with particular skills.
• Peak time balancing
The company envisages that the system could automatically enforce constraints when approving holiday requests. When it isn't possible to approve a holiday request because this would break a constraint, the system should suggest an alternative.
The company has several departments: Engineering, Plumbing, Roofing, Carpentry, Bricklaying, Finance and Personnel Office.
An employee works for a particular department, but in addition an employee will hold one of the following roles within their department:
• Head
• Deputy Head
• Manager
• Junior member
• Senior member
Every department has only one head and deputy head but has multiple members of all other roles.
The system needs to record details of all employees, which includes an employee's personal details, as well as the date when an employee joined the company.
The holiday entitlement for an employee is based on how long he/she has worked at the company. All employees get 30 days of holiday per year, plus one extra day for every 5 years an employee has been with the company.
The following constraints have been identified by the company which apply at all times:
• No employee can exceed the number of days of holiday entitlement
• Either the head or the deputy head of the department must be on duty
• At least one manager and one senior staff member must be on duty
• At least 50% of a department must be on duty
There are some exceptions which are that none of these constraints apply between the 24th of December to the 2nd January of every year.
In the month of August, the constraints are relaxed such that only 40% of a department must be on duty.
The following periods are considered peak times:
• 15th of July to 31st of August
• 15th of December to 22nd of December
• The week before and after Easter, which changes each year as Easter falls on a different day each year
When staff apply for holiday the system should prioritise staff who have had a lower number of holidays in the current year, followed by those who have fewer days in the peak time periods.
The company is controlled by the Board of Directors. The Board of Directors believe that by creating aholiday booking application will increase the efficiency and productivity of the company. The president of the company, Mr Smith and the head of the Finance and Personnel Office, Mr Brown, fully support the decision of the Board of Directors. They indeed believe that having such an automated system will increase productivity.
However, the other departments' staff, are not particularly keen on the development of the computerised holiday system. Most of them have been working in construction for years and therefore they prefer sticking to their old way of working (asking managers for leave), rather than having to deal with computers. They are reluctant to go through training and they do not see the value of an online system. They are also quite disappointed with the Board of Directors for proposing this and are afraid that they might not get the whole holiday days they are entitled.
In the long-term Straight Walls Ltd management wants to develop an app which its employees can install on a mobile phone or tablet. They are envisaging that employees could also use the app to request their holidays. The company is not sure yet what technology to use for the app, so for the prototype they are happy you build any application (desktop , on line ,etc), which would later be replaced with a mobile app.

Your team has agreed with the client to produce the prototype system.As a group you need to decide what software system methodology you will follow and identify the roles necessary for that mythology. For example:
• For traditional methodologies: developer, business analyst, project manager, tester, etc
• for SCRUM methodology : Product Owner (your tutor), Development Team( cross functional, small and self-organizing team), and Scrum Master.

Each member of the team should take lead on at least one role. However, every member of the cw team should do all the work and attempt every single task of the cw. The work should not be split between members, as most likely this will result to poor work overall.

The CW Team purpose is to discuss each of your solutions and then choose the best one (or a combination of them). The fact that other members in the group do not do their work will not justify you not doing the work. The grades are individual based on each team member contribution to each task.
 
Requirements -PHASE 1

After eliciting the initial requirements for the new system, your team has agreed with the clientto produce a preliminary design using traditional, structured methodologies, covering the functionality of the proposed new system. This is to be used to build a prototype database implementing the persistent storage part of the design. The prototype database is to be built using any competent technology/tools you are familiar with.

Deliverables for PHASE1: STRUCTURED ANALYSIS-DESIGN

Produce a preliminary design using traditional, structured methodologies, covering the functionality of the proposed new system described in the case study. The design should include:
• Entity Relationship Diagram which represents the Conceptual Data Model of the scenario described in the coursework spec as modified by elicitation discussions with the client. You are required to distinctly show:
o all entity types, attributes (including primary key attributes),
o all relationships,
o as well asdetermine the structural constrains (cardinality and participation constrains) of each relationship.
• Data Flow Diagram which represents the Process Model of the same specific functional area that you modelled for the Entity Relationship Diagram. You are required toinclude the DFD level 0 (context diagram).

Implement a database based on the design produced as per above requirement.
• The prototype database is to be built using any competent technology/tools you are familiar with. MS Access is fine for a prototype.
• The DB should provide enough functionality to be able to run the following SQL queries:
o Add / update/delete an employee. The employee must belong to a department.

You group is required to present and discuss Deliverables for Phase 1 with your client (your tutor) duringone your lab hours (during 18/02 - 4/03).

Requirements - PHASE 2

After the successful delivery of the "first cut" design of the proposedholiday system and prototype database specified in Phase 1, you have been retained to work on a more detailed design of the system.

You are required to design and build the system using object-oriented(OO) methodologies, to allow for more flexible design/build iterations and re-use of design and code. You have therefore now been asked to produce a design of the new system using object-oriented analysis and design principles and UML.

The OO software system shouldincorporate all required functionality including:
• View a list of outstanding holiday requests
• Accept/reject a request. When a holiday request is accepted or rejected it should be removed from the list of outstanding requests.
• View a list of all holiday bookings and filter them by employee
• Select a date and show all employees working that day and those on leave that day.

The systemprototype is to be built using any OO technology/tools you are familiar with. The system will need to have enough business and UI functionality to test the competence of the design for the main functionality of the system (the main/top level use cases).
Deliverables for PHASE2 (due by the submission date)
1) A final report (~3000 words) which should include:
a) A discussion regarding the 5 Ps relevant to the given case study
i) Problem(~500 words):
• a short description
• a brief evaluation of the commercial risk presented by the implementation of the new system
• a rich picture
ii) Process(~ 800 words):
• A discussion of the software system methodology you followed. Please choose at least one traditional and one agile methodology and argue your choice based on research. Include a section on how you fulfilled all the roles necessary for the chosen methodology within the group.
iii) Project (~500 words):
• state the goal of the system, a list of resources, and a breakdown of the budget (providing the framework within which management can be exercised).
• include a brief discussion regarding the suitability of any tools used (such as CASE tools, environments, systems and programming languages proposed)
iv) Product (~500 words).:
• State the artefacts that are created during the life of the project, such as models, source code, executables, and documentation.
• A list offunctional and non-functional requirements
v) People (~100 words).: describe the prime movers in the software project

b) The UML design, including:
i) Use Case Analysis - A UML Use Case diagram identifying all actors and their Use Cases. The use-case should also indicate any included or extended cases
ii) Interaction Diagrams. Using UML sequence (interaction) diagrams perform an analysis of the main Use Case scenarios
iii) Design UML Class Diagram - Show all attributes, all methods and associations for all main classes. (this should not be a Conceptual UML Class Diagram)
c) A discussion about the use of Design patterns in your design, with examples. You are expected to introduce patterns in your design, discuss about how these are used and consequently show how these are implemented in your code(~600 words)
d) An appendix with
i) Deliverables for PHASE 1.
ii) screenshots of the prototype
iii) listings of any code written by your group (no generated code, please)
iv) A personal discussion regarding your role and contribution within the group.
e) Completed copies of the Self-Assessmentform found included in the coursework specification. As a group you need to pear-assess each other's work and critically discus the quality of each completed task.
f) A completed copy of the work breakdown form on the last page of this document.As a group you will fill in and attach to the report a pro-forma (from the end of this document) that will enumerate all the tasks that your group tackled and completed as part of this coursework, and the involvement of each member of the group in each task. This will be used in part to establish the individual contribution of each member of the group. The pro-forma must be agreed and signed by all members of the group.

2) A prototype of the system.
This should reflect your design. You will need to upload the System/code through the coursework web site (as a ZIP file) together with your report.

3) System prototype acceptance testing
As part of the software development cycle an acceptance testing will need to be carried out. Your group needs to demonstrate online to the client (your tutor) the design and prototype system you have built. You will be asked to demonstrate the required business functionality and to show the adherence of the implemented system to the submitted design.

Attachment:- Enterprise Software Engineering Development.rar