CO6021 Advanced Systems Analysis and Design

Module Assessment

 

Andrew Jones 0817804 E15003

4/12/2011

 

 

 

 


 

Contents

Task One. 3

Developing the System Proposal 3

Terms of Reference. 3

Scope. 3

Current System.. 3

User requirements. 4

Possible Solutions. 4

Costs. 4

Benefits. 4

Recommendations. 4

Types of requirements. 4

Functional Requirements. 5

Non-Functional Requirements. 6

Task Two Use case Text based and UML. 10

Booking a dance class. 10

Booking an upcoming event. 13

Other identified use cases. 15

Task Three. 16

Entity Relationship Diagrams. 16

Task Four User interface design, 19

Goals. 20

Task Five. 21

Appendix 1. 23

Payment System.. 23

Appendix 2. 24

Building the questionnaire. 24

What does the client want/need?. 24

Representation of problems with current system.. 24

Representation of functionality of new system.. 24

Appendix 3. 25

Questions Answered. 25

Clarifications and further questions. 25

 

Table of Figures

Figure 1 conceptual map of systems specification. 3

Figure 2 A use case overview of Customer interactions with the site. 10

Figure 3 UML use case for booking and upcoming event. 13

Figure 4 outline data flow diagram for proposed web site. 16

Figure 5 ERD For Upcoming Events. 17

Figure 6 Data stores. 17

Figure 7 Booking a Class. 17

Figure 8 Context Diagram.. 17

Figure 9 Process flows for the booking system.. 18

Figure 10 Level 1 Data flow fragments. 18

Figure 11 Use case for the administrative functions of the web site. 19

Figure 12 Booking a dance class transaction. 19

Figure 13 Proposed template for the web sites home page. 19

Figure 14 The existing corporate logo. 20

Figure 15 Iconography for the features of the web site. 20

Figure 16 ISD For the web site. 21

 

Table of Tables

Table 1 Functional Requirements. 6

Table 2 Non-functional Requirements. 9

Table 3 Text based use case for booking a Dance class, Adapted from figure 5-6 page 161 (Dennis, Wixom, & Roth, 2006)  12

Table 4 Text based use case for booking an upcoming event. 15

 


 

Task One

Developing the System Proposal

This is the key deliverable from the Analysis Phase. A clear concise proposal is strategic to ensuring that the remainder of the project completes without problems. The systems proposal sets out two main areas of functionality: functional and non-functional. We currently have a comprehensive list of customer needs, wants and requirements, these have been conceptually mapped in the iconography shown if Figure 2. The questionnaire from which this iconography has been drawn is in Appendix 3.

Figure 1 conceptual map of systems specification

Terms of Reference

Paul Sullivan will act as the client and we will act as the developer, weekly meetings will ensure that the project runs to schedule and that the requirements detailed in the Requirements Specification are met. The project will be considered successful when all of the Requirements Specification are fully met.

Scope

For the project we will produce a web site that will: capitalise upon the existing online presence, advertise dance classes and upcoming events, enable customers to book and pay for classes and events, feature an e-mail contact form, be editable and choose random testimonials.

Current System

There is nothing in and of the current web site that the client wishes to retain other than the logo and the existing web presence.

User requirements

A modern fun and family orientated contemporary web site that promotes the dance classes and events available to customers. The web site should feature an e-mail contact form, booking and payments system together with randomly selected testimonials. The web site should be fully editable by the administrator and dance tutors.

Possible Solutions

Costs

The budget for the web site is £2,500 and the project must be complete within three months.

Benefits

The re-design of the web site will offer Raoul’s Dance Studio the opportunity to reposition them themselves as a fun, family orientated business offering dance classes and events to a wide range of potential customers. The re-design will capitalise upon the existing web presence and strengthen their position as a premiere brand.

Recommendations

That the client proceeds with the re-design of the web site and we the developers continue with the design proposal for the new web site, which will include: a booking system for dance classes and events, an e-mail contact form, randomly selected testimonials from customers, and an administrative interface allowing for full updates and changes.

Types of requirements

A requirement is a statement of what the system must do or what characteristics it needs to have. A functional requirement relates directly to a process the system has to perform or information it needs to contain. Non-functional requirements refer to behavioural properties that the system must have, for example performance and usability.

 


Functional Requirements

Requirement ID

Title

Type

Priority Level

Description

Target Value

AJ001

Online Web Presence

Functional

High

Re-design web site to develop and extend existing presence, incorporating the aspects required by the client of fun and family orientation

High ranking on Google search for certain keywords: such as: dance Chester, fun dancing and family dance classes

AJ002

Booking class

Functional

High

A simple to completed booking system for dance classes

Dance classes are booked for a specific customer

AJ003

Creating testimonial

Functional

High

A simple form for the customer to complete that endorses Raoul’s Dance Studio

Testimonials are added to a database of recommendations

AJ004

Booking events

Functional

High

A simple to complete booking form for events

Events are booked for specific customers

AJ005

e-mail contact form

Functional

High

A simple to complete web based e-mail contact form

Administrators and dance studio staff receive e-mails from the web site

AJ006

Advertise dance classes and events

Functional

High

The prominent positioning on the web site of dance classes and events

Dance class and events are booked by customers

AJ007

Upload images, videos and other file types

Functional

High

An interface for the uploading of images, videos and other file types

Images, videos and other files are successfully uploaded to the site

AJ008

Log on and edit all of the site

Functional

High

An administrative interface fop the editing of the web sites content

The web site if fully editable

AJ009

Fun and family orientated

Functional

High

The design of the web site should reflect that it is fun and family orientated

Customers enjoy themselves and families book classes and events

Table 1 Functional Requirements

Non-Functional Requirements

Requirement ID

Title

Type

Priority Level

Description

Target Value

AJ010

GUI design

Non-functional

Medium

The web site interface should be familiar, easy to understand and use

Customers book classes and events

AJ011

Marketing

Non-functional

Medium

The web site should capitalise upon the branding place with the site developed utilising the current corporate logo

Colour schemes for the site developed from the corporate logo

AJ012

Help File

Non-functional

Medium

The development of a help system for the administrative functions of the site together with help for booking a class or an event

Help files that detail how to make changes to the sight, how to upload files, and how to book a class or an event

AJ013

Training

Non-functional

Medium

Training for the administrator and dance studio staff on how to manage the site

The administrator and dance studio staff are able to upload files, change and edit site content and reply to e-mails

AJ014

Accessibility

Non-functional

Medium

The site will take into account the needs of a broad range of users and customers that may require larger fonts, or background colours

The site will feature the ability to change font sizes and the colour of the background

AJ015

Audit and control

Non-functional

Medium

 

 

AJ016

Availability

Non-functional

Medium

The web site should be constantly available 24 hours a day 7 days a week

The web site hosting package guarantees 24/7 availability

AJ017

Backup

Non-functional

Medium

Complete backups of the site should be made on a regular scheduled basis

Complete backup of the site and databases are made

AJ018

Disaster Recovery

Non-functional

Medium

The backups for the site can be restored to a different hosting provider in the event of a failure

Restoration of the site takes place

AJ019

Capacity Current and Forecast

Non-functional

Medium

The databases for the sight have the capacity to coop with the dance classes being run at full capacity and have room for growth

Ensure that the hosting package will allow for expansion in site content as well as offer database migration opportunities

AJ020

Deployment

Non-functional

Medium

The web site is deployed to a full featured web hosting provider

The web site is available to WWW users

AJ021

Documentation

Non-functional

Medium

A full, detailed specification and source code is available to Raoul’s Dance Studio

Documentation is produce and delivered to the client

AJ022

Extensibility

Non-functional

Medium

The sight is fully editable, and images and videos can be added

The sight grows with use

AJ023

Legal and licensing

Non-functional

Medium

The site should not make false representations or claims and it is the property of Raoul’s Dance Studio

The site is legal and belongs to Raoul’s Dance Studio

AJ024

Failure Management

Non-functional

Medium

In the event of a failure the site should be re-instated using a backup or the disaster recovery plan should be implemented

The site is quickly restored

AJ025

Interoperability

Non-functional

Low

The front end web site will interact with the backend databases seamlessly

The customer should not be aware that the sight is data driven

AJ026

Maintainability

Non-functional

Low

The administrative interface should allow for full editability

The site is fully editable

AJ027

Modifiability

Non-functional

Low

The administrative interface should allow for full editability

The site is fully editable

AJ028

Operability

Non-functional

Low

The site must function in all of the current web browsers

The site functions in all of the current web browsers

AJ029

Performance / Response time

Non-functional

Low

The site should have fast page loading

Pages are loaded in the shortest possible time

AJ030

Platform compatibility

Non-functional

Medium

The site should be browesable from any web enabled platform

The site is browseable from any web enabled platform

AJ031

Privacy

Non-functional

Medium

Personal details are kept in a secure password protected database

Compliance with the data protection act

AJ032

Portability

Non-functional

Low

The site should be deployable to any web hosting package

The site is deployable to any web hosting package

AJ033

Resource constraints

Non-functional

Medium

The project will take no longer than 3 months and cost no more than £2,500

The project is delivered on time and in budget

AJ034

Robustness

Non-functional

Low

The site should not fall over

The site should fail gracefully

AJ035

Security

Non-functional

Medium

Access to the customer areas of the site is password protected as is the administrative interface

Strong passwords are implemented

AJ036

Stability

Non-functional

Low

The choice of hosting package should reflect the need for constant availability and stability

The site is stable and secure

AJ037

Supportability

Non-functional

Low

The site should use standard code and be supported  by the developers for an agreed period of time

The site is supportable

AJ038

Testability

Non-functional

Low

A full featured test plan should be created to ensure cross browser and platform compatibility

The test plan

Table 2 Non-functional Requirements


Task Two Use case Text based and UML

Figure 2 A use case overview of Customer interactions with the site

Booking a dance class

Use case name: Booking a dance class

ID: 001

Importance level: High

Primary actor: Web site Visitor

Short description: This use case describes how a web site visitor can search for and book a dance class.

Trigger: web site visitor searches Web site for and finds dance class to book and pay for

Type: External                   Temporal

Major Inputs

Major outputs

Description

source

Description

destination

Search for dance class

web site visitor

Dance class matching search request

web site visitor

Dance class selected for booking

web site visitor

Dance classes selected for request

web site visitor

web site visitor information

web site visitor

Dance class information

web site visitor

Dance class availability

web site visitor

Booking

booking system

dance class information request               

web site visitor

Booking confirmation

web site visitor

 

dance class stock

dance class data store

Marketing and Promotional Materials

Marketing and testimonials data store

Major Steps Performed

Web site visitor enters dance class search request and receives a display of dance classes matching the request, weather it is searched for by dance type, variation, date, price, location, tutor or request from page link

Web site visitor requests and receives more information about one dance class. This starts with some basic information, but may also include extra marketing material, e.g. testimonials and video clips

Web site visitor requests dance class location list and receives dance studio list and the availability of the dance class in those studios’ schedule

Web site visitor selects the dance class at a studio by booking

Dance class selected for request

Web site visitor “checks out” confirming the dance class has selected, calculating the total amount and accepting customer name, contact information and payment details.

Dance class selected for request

Web site visitor receives confirmation of dance classes booked

Information for steps

Search request

Dance classes matching search request

Dance class marketing materials

Dance class availability by studio

Dance class selected for request

Dance class selected for request

Dance class selected for request

Dance class selected for request

Customer information

Reduce availability for dance class at studio

Studio reservation confirmation

Booking system

 

Table 3 Text based use case for booking a Dance class, Adapted from figure 5-6 page 161 (Dennis, Wixom, & Roth, 2006)

Booking an upcoming event

Figure 3 UML use case for booking and upcoming event

Use case name: Booking an upcoming event

ID: 002

Importance level: High

Primary actor: Web site Visitor

Short description: This use case describes how a web site visitor can search for and book an upcoming event.

Trigger: web site visitor searches Web site for and finds an upcoming event to book and pay for

Type: External                   Temporal

Major Inputs

Major outputs

Description

source

Description

destination

Search for an upcoming event

web site visitor

An upcoming event matching search request

web site visitor

An upcoming event selected for booking

web site visitor

An upcoming event selected for request

web site visitor

web site visitor information

web site visitor

An upcoming event information

web site visitor

An upcoming event availability

web site visitor

Booking

booking system

an upcoming event information request

web site visitor

Booking confirmation

web site visitor

 

an upcoming event stock

an upcoming event data store

Marketing and Promotional Materials

Marketing and testimonials data store

Major Steps Performed

Web site visitor enters an upcoming event search request and receives a display of an upcoming events matching the request, weather it is searched for by dance type, variation, date, price, location, tutor or request from page link

Web site visitor requests and receives more information about one an upcoming event. This starts with some basic information, but may also include extra marketing material, e.g. testimonials and video clips

Web site visitor requests an upcoming event location list and receives dance studio list and the availability of the an upcoming event in those studios’ schedule

Web site visitor selects the an upcoming event at a studio by booking

An upcoming event selected for request

Web site visitor “checks out” confirming the upcoming event has selected, calculating the total amount and accepting customer name, contact information and payment details.

An upcoming event sleeted for request

Web site visitor receives confirmation of an upcoming events booked

Information for steps

Search request

An upcoming events matching search request

An upcoming event information request

An upcoming event marketing materials

An upcoming event availability by studio

An upcoming event selected for request

An upcoming event selected for request

An upcoming event selected for request

An upcoming event selected for request

Customer information

Reduce availability for an upcoming event at studio

Studio reservation confirmation

Booking system

 

Table 4 Text based use case for booking an upcoming event

Other identified use cases

·         Adding a testimonial

·         E-mail contact form

·         Administrative GUI

·         File upload

·         Update GUI

 

Task Three

Figure 4 outline data flow diagram for proposed web site

Entity Relationship Diagrams

Figure 5 ERD For Upcoming Events

Figure 6 Data stores

Figure 7 Booking a Class

Figure 8 Context Diagram

A process the system has to perform

Figure 9 Process flows for the booking system

Information the system must contain

Figure 10 Level 1 Data flow fragments

Figure 11 Use case for the administrative functions of the web site

Figure 12 Booking a dance class transaction

Task Four User interface design,

Figure 13 Proposed template for the web sites home page

 

Goals

Figure 14 The existing corporate logo

Utilise current branding

Expand on their current online presence, focus marketing promotions about the fun and friendly orientation of the dance studio; make it simple to book classes with an integrated Google checkout system, see Appendix 1.

Figure 15 Iconography for the features of the web site

Figure 16 ISD For the web site

Task Five

Systems analysis is evolving, gone are the days of formal systems specifications, todays trend is towards an adhoc collection of “what works” from yesterday’s formal analysis methods as systems analysis and design embraces an increasing number of disciplines. Progressively more automated software agents will fill in the details of ERD, Data Flow Diagrams and UML models, analysts will concentrate on the fine tuning of these automated processes and software agents. Most business systems requirements will be carried out by the end user, with information systems analysts being reduced to the role of consultant or advisor. (Siau & Faulkner, 2007)

The Agile philosophy of systems development tends towards less formality, less documentation and even less use of models. This trend contradicts the model driven architectures which require more and more documentation and models. The result of this is a Unified Process which should be considered as both formal and adaptive, it attempts to combine the best of both camps. (Satzinger, Jackson, & Burd, 2009). Personally I am firmly in the adaptive faction.

We have through the process of completing this assignment learnt to implement the “hard skills” of process modelling necessary to develop a robust information system for a real world client with a genuine business need, what we have not covered are the “soft skills” which are associated with managing a project, interacting with teams and presentations.

In this assignment I have attempted to produce a visually attractive, practical approach to the tasks required and of systems development in general. Whilst not necessarily adhering to the standards for the preparation of the specific model types, (Dennis, Wixom, & Roth, 2006). I feel that my knowledge and ability to produce these diagrammatic models has improved significantly. As stated earlier I am of the adaptive faction of systems development which “holds that less is more and communication is the key”, in the production of this piece of work I have adopted a Rapid Application Development philosophy, with a focus on throwaway prototyping. The models and diagrams reflect a step, jump step approach to systems analysis and design that is becoming progressively prevalent in today’s information management systems.

The client wants a new web site, which is a case of the cart going before the horse. What the clients actually wants is more business! The desire for a web site as the answer to this business problem is weak, as any marketing guru will tell you, the most successful way to advertise and gain new business is through word of mouth, and people trust people, not web sites. Web sites are a one way transitive communications process that cannot be controlled; the client would be better served addressing the businesses profile. The development of these models reflects that the internet is king and that the web site is core to the success of the business. Rather, the nature of web sites is changing faster than the client can keep up with reflects this weakness in marketing communications. The business models of product/service orientation have gone, the Dance Studio needs to change its core business model to one of value added, and it is into this framework that a new web site should be considered. The dance studio is a traditional bricks and mortar business, not an internet dependant one, this implementation of online shopping and advertising should be considered in the broader context of people are naturally lazy, and the focus should be adding value to people’s lives, not necessarily advertising dance classes and events. (Shelly, Cashman, & Rosenblatt, 2010)

All things being equal, I have enjoyed then work necessary to completing this assignment, whilst stretching the boundaries of what is considered “the correct” approach I have learnt that systems analysis is a dynamic evolving process that shouldn’t be constrained by the past requirements of formalisation in documentation or modelling. There have been enough spectacular failures in systems development to prove to me that the traditional methods, whilst some time necessary, are not the panacea.


 

Appendix 1

Payment System


 

Appendix 2

Building the questionnaire

What does the client want/need?

1.       What do you value most in the current system?

2.       What is the primary message you wish to convey to your audience with this site?

3.       What are the secondary objectives you hope to achieve?

4.       What are the overall goals you intend to reach with this site?

5.       Who is your target audience?

6.       Use three adjectives to describe how the site should be perceived by the user.

a.        (Examples: conservative, progressive, friendly, formal, casual, serious, energetic, humorous, professional)

7.       What is the primary action you wish your target user to take from the main page of your site?

a.       (Examples:  download, browse, move along a specific path, email, order, explore, click button, and call via phone, Etc.)

Representation of problems with current system

1.       Why are you unable to get access to current site?

2.       What of the old site is still actually wanted or needed?

3.       Why is the design poor?

4.       Are there any examples of site that he likes the look and style of?

Representation of functionality of new system

1.       How many people will have access to the system?

2.       How big do you want the system to be?

3.       How long do you think the project will take?

4.       What are the most important areas for the new system to deliver to be considered as successful?

5.       What degree of training do think would be appropriate?

6.       What budgetary resources are available for the project?

7.       What do you want most from the system?

8.       What information do you need from the new system that you do not have currently?

9.       Is there any corporate banding in place that needs to be integrated into the site?

10.   Given a screen is 100% how much space, in percentage terms, to allocate to the advertising of dance classes?

11.   How much screen real estate, in percentage terms, to allocate to upcoming events?

12.   How much space to allocate to testimonials, in percentage terms?

13.   Are we designing for a specific size of browser window? e.g. 1024 x 768 pixels would give a design space of 955 x 600 pixels

 


 

Appendix 3

Questions Answered

1.        What do you value most in the current system?

The online presence. Apart from that there are very few areas I would consider valuable.

2.        What is the primary message you wish to convey to your audience with this site?

I wish to convey that we are a dance studio offering events, classes for children and adults

3.        What are the secondary objectives you hope to achieve?

Drive customers to my business

4.        What are the overall goals you intend to reach with this site?

A better design, greater features, payments system, advertising of events and classes

5.        Who is your target audience?

Children and their parents

6.     Use three adjectives to describe how the site should be perceived by the user.

(Examples: conservative, progressive, friendly, formal, casual, serious, energetic, humorous, professional)

 

Dance oriented, Fun, Friendly

7.     What is the primary action you wish your target user to take from the main page of your site?

(Examples:  download, browse, move along a specific path, email, order, explore, click button, and call via phone, Etc.)

Book classes

8.     Why are you unable to get access to current site?

It was static but has since been taken offline.

9.     What of the old site is still actually wanted or needed?

My logo must be present. Apart from that nothing

10.   Why is the design poor?

See attachments

11.   Are there any examples of site that he likes the look and style of?

No specific. you have full reign on design apart from the logo being required

12.   How many people will have access to the system?

Admin * 1

 

Tutors * approx. 8-12 dependant on who I am employing (and these change frequently)

13.   How big do you want the system to be?

I don’t understand the question

14.     How long do you think the project will take?

It must be completed in 3months

15.     What are the most important areas for the new system to deliver to be considered as successful?

User editable, Payments system, good design

16.   What degree of training do think would be appropriate?

A guide where required and special instruction for complicated bits + initial setup

17.   What budgetary resources are available for the project?

£2500

18.   What do you want most from the system?

All the features I described

19.   What information do you need from the new system that you do not have currently?

Users, visitors, payments, emails

20.   Is there any corporate banding in place that needs to be integrated into the site?

No apart from the logo

21.   Given a screen is 100% how much space, in percentage terms, to allocate to the advertising of dance classes?

I would like an entire section allocated

22.   How much screen real estate, in percentage terms, to allocate to upcoming events?

Full section

23.   How much space to allocate to testimonials, in percentage terms?

Full section

24.   Are we designing for a specific size of browser window? e.g. 1024 x 768 pixels would give a design space of 955 x 600 pixels

I am a dance tutor - what’s a pixel?

Clarifications and further questions

13.  How big do you want the system to be?

You’ve said that you expect there to be 1 admin and up to twelve users, are these maximum numbers? How big do you expect the customer base to grow too? How many visitors do you expect per day/month/year?

24.   Are we designing for a specific size of browser window? e.g. 1024 x 768 pixels would give a design space of 955 x 600 pixels

Sorry a pixel is a unit of measurement for an area of the screen, think of it as a millimeter or centimeter. It gives us a boundary size in unit terms. i.e. 1024 x 768 = 786432 units squared, picture graph paper if you will.

You’ve placed a high importance value on e-mail, are these just to you as administrator or distributed to the users as well?

Do the users have spate user e-mail address?

 


 

Bibliography

Dennis, A., Wixom, B. H., & Roth, R. M. (2006). Systems Analysis and Design (Third ed.). (B. L. Golub, Ed.) Hoboken, New Jersey, USA: John Wiley & Sons Inc.

Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2009). Systems Analysis and Design in a Changing World (Fifth ed.). (A. v. Rosenberg, Ed.) Boston, MA, USA: Course Technology.

Shelly, G. B., Cashman, T. J., & Rosenblatt, H. J. (2010). Systems Analysis and Design (Eighth ed.). (K. McMahon, Ed.) Boston, MA, USA: Course Technology.

Siau, K., & Faulkner, J. E. (2007, May 06). Systems Analysis and Design - Trends and Directions. Interlaken, Switzerland.

 

Works Cited

Dennis, A., Wixom, B. H., & Roth, R. M. (2006). Systems Analysis and Design (Third ed.). (B. L. Golub, Ed.) Hoboken, New Jersey, USA: John Wiley & Sons Inc.

Satzinger, J. W., Jackson, R. B., & Burd, S. D. (2009). Systems Analysis and Design in a Changing World (Fifth ed.). (A. v. Rosenberg, Ed.) Boston, MA, USA: Course Technology.

Shelly, G. B., Cashman, T. J., & Rosenblatt, H. J. (2010). Systems Analysis and Design (Eighth ed.). (K. McMahon, Ed.) Boston, MA, USA: Course Technology.

Siau, K., & Faulkner, J. E. (2007, May 06). Systems Analysis and Design - Trends and Directions. Interlaken, Switzerland.