COMP 1648

To help meet this requirement, DSDM will help set the quality level from the beginning and ensure that it does not become a variable.. Below are the high level requirement I think that n

Đỗ Văn Long – GCH15158

Development Frameworks and Methods

Section A – Management Summary

Walk2Live is a health and fitness franchise that has been steadily growing over the last 20 years that was founded when Janet Moore and six of her friends The company has since evolved from being a walking club to being a wellness center, offering classes, such as spinning, yoga and pilates, in addition to the walking and running clubs Furthermore, the brand has created their own health food and supplement range that is sold at the centers Some centers have also opened up juice bars where members can socialize after class

Currently Walk2Live has a head office, employing 15 people, as well as 55 franchises in different towns and cities across the UK Each franchise is responsible for their region and this is managed locally, either manually, through spreadsheets, or a simple website connected to a database Many centers also need to liaise with charities to host walkathons, and are subject to the terms and practices of each respective charity Marketing materials and health products are distributed from the head office to each center as needed

The center decided to build a system to manage the franchises centrally, and also to allow each franchise to manage their own operations in a more structured fashion However, this resulted in only a basic website with none of the functionality that the center need

A new system called Alive will be developed, that the new system would allow a franchise

to keep track of their own members, classes and programmers, and would also include an ordering system for marketing materials and the health food and supplement range In addition, the system would help those franchises that have links to charities to manage those relationships

as well The center expects the system to be completed and can operate within 4 months

Based on the scenario, the problem of Walk2Live is that the old system does not meet the functions that the center desired Therefore, the center wants to develop a new system that meets the functions they desire These function will focus on business purposes, linking affiliates and will be referenced from the members of the organization In addition, the center wants the system can be operational for 4 months From the above analysis, I think the use of DSDM Atern method to approach the project is reasonable It is shown in detail through the following eight principles:

1 Focus on the business need: According the scenarios, Walk2Live is a wellness center,

offering classes, such as spinning, yoga and pilates, in addition to walking and jogging clubs Moreover, the brand has created its own health food and range of supplements being sold at the center Some of the centers have also opened fruit juice bars where members can exchange after-school So that, the system will be developed to serve the organization's business requirements Therefore, DSDM is the perfect approach for business service It helps to distribute what businesses need and establish sound Business Case

2 Deliver on time: Delivering the product on time is what the organization wants and is

an important success factor By using DSDM, it will provide time-boxing techniques to divide project work into blocks that always focus on business priorities Time-boxing requires that the product be delivered at the end of each time-box, so the product is always hit deadlines

3 Collaborate: To complete the system, the development team needs to get more

information from the members of the organization Collaboration here is so important that it encourages increased understanding, faster pace To ensure collaboration, DSDM will help to link stakeholders, at the right time, throughout the project; ensure that members of the group are empowered to make decisions on behalf of the people they represent; actively consult with business representatives and build a group culture

4 Never compromise quality: According the scenarios, Although Ben was keen to have

the full system developed before the end of the year he was hoping to get that part

of the system up and running within 4 months To help meet this requirement, DSDM will help set the quality level from the beginning and ensure that it does not become

a variable Quality building is done by continuous review and everything is checked as soon as possible

5 Build incrementally from firm foundations: The system has some requirements that

need to be implemented but have lower priority These requirements do not need to

be implemented immediately but should be made when the prototype is completed and approved The application of DSDM approach in this case is very reasonable Under these principles, the remaining requirements of the system can still be fully deployed to the system when the most important requirements are implemented and approved

6 Develop Iteratively: In the development process, changing the system requirements

is inevitable When applying the DSDM approach, it allow change and exploit the benefits of such changes Within the constraints of time and cost, changes are encouraged to provide the most appropriate solution for the system DSDM uses iteration and constant review to ensure that what is being developed is what the business really needs

7 Communicate continuously and clearly: According the scenario, the development

team needs to adopt the opinions of the members of the organization Again the application of the DSDM approach is reasonable It emphasizes the value of human interaction through stand-ups and clearly identifies the role and involvement of the user In addition, it provides rich communication techniques such as modeling and modeling to create the first versions of the solution available to monitor and encourage informal, face-to-face communication at all level

8 Demonstrate control: Control is needed for a project According to DSDM, projects

must be controlled at all times The use of Time-boxes is clearly defined, with continuous rating points being sent to the parties involved

Based on the scenario and the above analysis, I can point out the benefits that DSDM brings to the development of the Alive system:

 The Walk2Live executives committee do not have to worry about the development of the system as it has been assigned to the development team

 All members of the organization are involved in the development of the system

So they can see their ownership, lead to increasing the sense of responsibility

 The system will be divided into small projects and independently developed Therefore, each bug in a small project does not affect the system

 MoSCoW Priority allows critical transactions to be completed first in a given time provided by the time-box

Although DSDM is the right approach to the system However, it still has disadvantages affecting Walk2Live:

 Because DSDM allows for repeatable development and encourages users to provide changes at any time Therefore, if this happens too much it will lengthen the time and increase the budget

 Making a decision will be difficult because it depends on the development team

 Collaboration can be difficult when the members of the organization do not want

to participate This problem can affect the development of the system

Section B – High level requirements analysis and MoSCoW prioritization

B1 Review the ‘high level requirements’ list given at the end of Appendix A

B1.1 Identify any of the requirements that you feel are not appropriate high level requirements, giving your reasons for this

Below are the high level requirement I think that not appropriate with the new system of Walk2Live – Alive:

 The site should be easy to use and quick to load This is a non-functional requirement, which focused on developing fast, user-friendly system So it's not a

business requirement, but business can still run without this requirement Therefore, this requirement will not be high level requirement

 We need to register the web URL Walk2Live.co.uk The same is also a non-functional requirement not related to business requirements Therefore it is not appropriate a high level requirement

 Customers must be able to log in This is a functional requirement but it not appropriate a high level requirement Because, high-level requirements should include multiple transactions, “login" is only data entry transaction

 User can register with their e-mail address and log in so we can have their details

to send them marketing materials The same “login”, “can register with e-mail address” also is only data entry transaction So it is not appropriate a high level requirement

 For the most part we can use the system I have already written You just need to write the code to connect the database to the frontend – I’ve already created the database in MS Access This requirement does not provide functions, constraints,

or business rules to meet the needs of the business In other words, this request

is a user story but does not state the role of the request So it is not appropriate the high requirements

B1.2 Rewrite, and add to, the list to end up with a total of 10-12 high level requirements that you feel are required for building the system Briefly justify the need for each of your high level requirements against information you have gathered from the case study

Based on the list of requirements are provided and my knowledge, I have compiled a list

of the high level requirements required to build the system The list includes the following requirements:

 The system must display the product information with the image This is an

important function for an electronic commerce site It gives customers easy approach to the product It includes a set of transactions such as retrieval, updating of data, etc Therefore, it is a high level requirement

 Customers can view details of products, order and purchase products This

feature makes increase customer interoperability and boosts sales by selling online So, the function is a business requirement and it also includes a set of transactions Therefore, it is a high level requirement

 Customers can pay online by bank card or electronic wallet This is an important

function in making online sales that help diversify payment methods, creating favorable conditions for customers So, the function is a business requirement and

it also includes a set of transactions Therefore, it is a high level requirement

 Users can review and comment on each product This function is important in

helping to improve product quality and interact with customers

 Users can feedback about the quality of products and services to administrators

through the system, email, hotline This function is important in helping to

improve product quality and interact with customers

 Administrators can work and manage with the database This is an indispensable

part of the system, which makes it easy for administrators to manage objects

 Administrators can view reports on product and revenue of each store's This

feature will help administrators keep track of the business situation of the organization and can offer the next development plan

 The system must integrate accounting services This feature makes calculations

easier, saving time for employees and reduce the possibility of errors at the lowest level

 The system must link to the branch store This is an important feature that helps

administrators grasp the situation of each store when accessed from anywhere Customers can also find and shop at the store they want on the system to reduce shipping costs

B2 Use the MoSCoW rules to prioritize the requirements in your updated ‘high level requirements list’

B2.1 Produce an updated ‘high level requirements list’ clearly showing the prioritization you have given to each of your requirements

1 Customers can sign up for the account, confirm the information,

and sign in

Should have

2 The system must display the product information with the image Must have

3 Customers can view details of products, order and purchase

products

Must have

4 Customers can pay online by bank card or electronic wallet Should have

5 Users can review and comment on each product Should have

6 Users can feedback about the quality of products and services to

administrators through the system, email, hotline

Should have

7 Administrators can work and manage with the database Must have

8 Administrators can view reports on product and revenue of each

store's

Must have

9 The system must integrate accounting services Should have

11 The system must be multi-platform integrated Must have

12 The system must have a nice interface and easy to use Should have

B2.2 Explain how you set about prioritizing the requirements and justify your reasons for the decisions that you made

Customers can sign up for the account, confirm the information, and sign in: Allowing

customers to register for an account and authenticating customer information has priority

"should have" because it needs to be prioritized, however it is not essential to the system The system can work well without it but if it does it will increase the efficiency and value for the system

The system must display the product information with the image: For an e-commerce

website, the display of the information of products on the system is indispensable If this is not done the system seems to fail

Customers can view details of products, order and purchase products: This is a

mandatory function because allowing customers to view product details and buying it is an indispensable function in an ecommerce website Without this function the purpose of the website would not be achieved

Customers can pay online by bank card or electronic wallet: Allowing customers to pay

online is supposed to "should have" in the system because this function will increase the value

of the system and boost sales of online sales However, if this function is not implemented the system can still meet its purpose

Users can review and comment on each product: Customer feedback and product

reviews will help the system better interact with the customers, thereby improving the quality of the customer experience However, it does not affect the efficiency of the system So it has the priority "should have"

Users can feedback about the quality of products and services to administrators through the system, email, hotline : Similar to allowing customers to comment on the product, receiving

customer feedback will help the system better interact with the customers, from that provide a policy to fix and improve However, it does not affect the efficiency of the system, so it has the priority "should have"

Administrators can work and manage with the database: Allowing the administrator to

work with the database is an integral part of the system Part purpose of the system is to make managing the business easy So if this is not implement, the system will probably not work and failure

Administrators can view reports on product and revenue of each store's…: To optimize

all the tasks that help administrators capture the situation and manage their work easily, allowing them to view reports is indispensable This requirement is important so it needs to be set to the

"Must have" priority level

The system must integrate accounting services: In business, calculation is indispensable,

so integrating accounting services into the system is very important It reduces the cost and time spent on this task, thereby increasing system efficiency and accuracy However without it, the system also can work stably and efficiently, so this requirement has the priority "Should have"

The system must link to the branch store: Because the organization has many different

branches, so linking the branches is indispensable It help the system has uniform database and easy to manage from the center It is also the purpose to this system to be built, so it needs to be set to the "Must have" priority level

The system must be multi-platform integrated: This feature makes the system accessible

from a variety of devices such as phones, PCs and on various operating systems So that, In order for the system to work well for every user, every device accesses - cross-platform integration is indispensable to an e-commerce website today

The system must have a nice interface and easy to use: For a website, interface is very

important, it determines whether customers want to stay or not Therefore, professional and optimized interface design is very necessary However, with a normal interface, the system can still work effectively Therefore, this requirement will be set at the "Should have" priority level

Section C – Legal, Social, Ethical and Professional issues

C1 – Considering Legal, Social, Ethical and Professional Issues (LSEPI)

To an organization can sustain its operations must adhere to legal, social, ethical and professional issues The law would cover legal issues, and everyone must follow the rules in the law Every organization has its own legal, social, ethical and professional issues This section discusses and clarifies the legal, social, ethical and professional issues of W2L

Law:

 Cookies – laws and consumer perception on placing these

 Privacy of personal information entered on a web site

 Sending unsolicited e-mail

 Replying promptly to e-mail

 Copyright

 Site content and promotional offers/adverts are in keeping with the different laws

in different countries

Social, ethical:

 Providing text, graphics and personality in keeping with social mores of different countries

 Are we limiting access to information from certain sections of society (social exclusion)?

Professional Issues:

 An Accepted Body of Knowledge

 Structured Training

 Skills Maintenance and Development

 A Code of Conduct and Practice