middleshire university proposal

SAPPHIRE SOLUTIONS

MIDDLESHIRE UNIVERSITY MOODLE

CUSTOMIZATION PROJECT

Response to RFP

SAPPHIRE

SOLUTIONS

Middleshire University Moodle Customization Project

© 2014 Sapphire Solutions 2 | P a g e

Project Owners: Middleshire University

FAO: E. Duncker

Procurement Manager

Document Version: 1.0

Abstract: Middleshire University Moodle

Customization Project

Prepared By: Sapphire Solutions

Date: 10th May, 2014

Contact / Team Members: Sapphire Solution

Nwabueze Vitalis N - M00479877

Moronkunbi Mubarak A - M00373192

Okpala Samuel Okwudili - M00473841

Okiche Emmanuel Mbanefo - M00471857


CONTENTS

EXECUTIVE SUMMARY ........................................................................................................................................................ 5

INTRODUCTION ................................................................................................................................................................... 5

APPROACH AND METHODOLOGY ....................................................................................................................................... 6

PRINCE2 ............................................................................................................................................................................... 6

SCRUM ................................................................................................................................................................................ 6

PROJECT DELIVERABLES ...................................................................................................................................................... 7

The project encompasses the development of Studynet for Middleshire University. The following deliverables are all

included in the project: ....................................................................................................................................................... 7

Below Is the WBS for Studynet ........................................................................................................................................... 8

WBS FOR STUDYNET ........................................................................................................................................................... 8

THE GANTT CHART FOR STUDYNET .................................................................................................................................... 8

THE NETWORK DIAGRAM FOR THE STUDYNET .................................................................................................................. 8

PROJECT CRITICAL PARTS .................................................................................................................................................... 8

RESOURCE REQUIRMENTS AND ESTIMATED COSTING ....................................................................................................... 8

PROJECT TEAM WORK HOURS AND COST .......................................................................................................................... 8

SUPPORT AND MAINTENANCE AGREEMENT CONTRACT ................................................................................................... 8

1.SUPPORT SERVICES: The nature of the Support Services rendered will include the following activities: .......................... 8

2.TERMS OF AGREEMENT: This Agreement shall be effective when signed by both parties and shall remain legal, for a

period of 12 months subject to performance in accordance with the obligations of the two parties. ................................. 9

PAYMENT .......................................................................................................................................................................... 10

APPROACH TO QUATITY ASSURANCE: .............................................................................................................................. 10

PURPOSE ........................................................................................................................................................................... 10

REFERENCE DOCUMENTS ................................................................................................................................................. 10

MANAGEMENT ................................................................................................................................................................. 10

DOCUMENTATION ............................................................................................................................................................ 11

STANDARDS, PRACTICES, CONVENTIONS AND METRICS .................................................................................................. 11

SOFTWARE REVIEW........................................................................................................................................................... 11

TESTING ............................................................................................................................................................................. 12

PROBLEM REPORTING AND CORRECTIVE ACTIONS ......................................................................................................... 12

TOOLS, TECHNIQUES AND METHODOLOGIES................................................................................................................... 13


SUPPLIER CONTROL........................................................................................................................................................... 13

RECORDS COLLECTION, MAINTENANCE AND RETENTION ............................................................................................... 13

TRAINING .......................................................................................................................................................................... 14

RISK MANAGEMENT ......................................................................................................................................................... 14

Glossary ............................................................................................................................................................................. 14

APPENDIX 1, SUPPLIER COMPANY OVERVIEW ................................................................................................................. 14

TEAM MEMBERS AND ROLES ............................................................................................................................................ 16

APPENDIX 11, REFERENCES OF PREVIOUS WORK ............................................................................................................. 16

APPENDIX III, ACCOUNT MANAGEMENT & CONTACT ...................................................................................................... 17

AGREED MEETING PLAN, DATES AND TIME ...................................................................................................................... 17

APPENDIX IV, QUALITY ASSURANCE ................................................................................................................................. 18

TESTING ............................................................................................................................................................................. 19

PROBLEM REPORTING AND CORRECTIVE ACTIONS .......................................................................................................... 19

APPENDIX V, DETAILED SPECIFICATIONS OF THE PRODUCT ............................................................................................. 20

Functional Requirements .............................................................................................................................................. 20

Non-Functional Requirements ...................................................................................................................................... 21

Front-End ...................................................................................................................................................................... 21

References ............................................................................................................................................................................ 21


EXECUTIVE SUMMARY

The main aim of the Studynet project is to develop an environment that contains a variety of real world

setting that enables either individual or students of Middleshire University with learning disabilities to

learn and practice important living skills with an ultimate goal of preparation for the students learning

outcomes.

Some modules of the Studynet page were completed: learning materials environment for students,

modules information, student’s assessment, auto plagiarism check, communication among modules and

advanced level of system of user accounts.

The project as a whole applied a user centred approach to design and assessment of the Studynet design

specification for the whole interface of the Studynet.

The important objective of the Sapphire Solutions project is to assist the growth and enhancement of

real world skills. However, it was noticed that there may be many factors influencing learning from use

of Studynet page environment.

For example, usability and access issues would have a huge influence on learning from any computer-

based programme.


INTRODUCTION

Having understood the RFP, Sapphire Solutions is proposing a solution called Studynet developed

from Open source software called Moodle. Moodle is a Content Management System "CMS"

package designed using sound pedagogical principles, it help educators create effective online learning

communities.

Aims and Objectives

Our aim for this project is to design and create an open source application for Middleshire University

which will be easy to use and access. This service will render the management of online module

content in all available formats. The content covers general module information, learning materials and

assessment. It will enable student’s submit assignments and get feedbacks in due course. We will also

create fields for grading of assignments with a variety of grading methods including direct grading,

rubrics and written feedbacks.

The objectives of this project shall include but not limited to

1. Online module content in all available format

2. Content delivery for course information


3. Automatic plagiarism checks of all submitted texts with a similarity index and a detailed report.

4. Grading of assignments with a variety of grading methods including direct grading, rubrics and

written feedback

5. Intended use is group work, collaboration, communication, sharing, activities, and critical

reflection, a collaborative type of learning.

6. Communication among module participants in the form of email, blogging, commenting and

feedback

7. Provide a service for students who increasingly look to the internet as the natural medium for

finding information and resources.

8. A system of user accounts with advanced access level system,

9. A knowledge base about the module content, a diary and a calendar.

APPROACH AND METHODOLOGY

Sapphire Solutions will use the Agile Method as the project management approach. This model is one

that emphasizes the rapid delivery of application in complete functional components. This

methodology makes it create tasks and organize; all time is “time-boxed” into phases called “sprints.”

With this method, testing and debugging is easier, because after each the customer has frequent and

early chances to see the work being delivered, and to make decisions and alterations throughout the

development project, if time to make specific plugin is a concern, Using Agile Method, “sprint” plugin

can quickly produce a basic version of working software. Based on the fact that Development is often

more user-focused, likely a result of more and frequent direction from the customer

We have the opportunity to use the PRINCE2 approach merged with SCRUM under the AGILE

framework to achieve our said objectives in this project. The deliverables shall be provided according

to the approaches because of their ‘individual interaction over processes and tools, working software

over comprehensive documentation, collaboration over contract negotiation with customers, responds


to change following a plan, focused on business justification, flexibility that can be applied at a level

appropriate to the project’ and many more advantages.

PRINCE2

Prince2 Project management methodology being generic, scalable and independent is a method that

supports organizational control over investments in projects. During our discovery that this approach

was developed by the United Kingdom government agency office of Government Commerce (OGC),

our confident was risen on it, stimulating us to research more, thereby discovering its rich features for a

robust and medium Software project management capability.

PRINCE 2 methods also provide project with structured roles and accountability, as each person in the

project team knows what is being expected of them which makes the process task completion easy and

straight forward. This approach allows focus on the product and also to give progress report to the

project board and clients in order for everyone involved in the project to have an idea of the end

product. Prince2 provides the ability to learn and to promote continual mind-sets. Because in

PRINCE2, production team are expected to learn at the start of the project, during the project and at the

end to provide a lessons log and pass on lessons for other subsequent projects.

SCRUM

Unity being one of the strongest strength of the Scrum team, not only that, the team are basically self-

directed, their operation is in successive one-month iteration, holding of daily meetings also gives the

team a better insight to quickly identify a problem and quickly tackle it for solution. The scrum

approach is always having something (demo) to show to the client, this is good in the sense that, there

can be an immediate modification of work done. (Wyscoki, 2009, p.451) describes in his book that the

scrum approach is most suitable in a client-driven application. Our most basic reason for wanting to

apply scrum is the ability to apply the already engineered practices in an organization. Meaning that, it

involves frequent management activities aiming at consistent identification of insufficiencies or

weaknesses in the development processes as well as the practices that used.

Finally, the combination of the both approaches will be helping us to identify our flaws and quickly

adjust to fit in both approaches will be guiding and leading our team on unity while working,


PROJECT DELIVERABLES

The project encompasses the development of Studynet for Middleshire University. The following

deliverables are all included in the project:

Assessment grading system

Electronic students and tutors records

Plagiarism checker

Online Library

Instant access to student performance

Online fee payment

Information and result checking


Below Is the WBS for Studynet

WBS FOR STUDYNET


THE GANTT CHART FOR STUDYNET


THE NETWORK DIAGRAM FOR THE STUDYNET

PROJECT CRITICAL PARTS

RESOURCE REQUIREMENTS AND ESTIMATED COSTING

The costs for the project have been evaluated by experts from Sapphire Solutions, and have been able

to come up with the following estimate for the proposed Studynet.


PROJECT TEAM WORK HOURS AND COST

SUPPORT AND MAINTENANCE AGREEMENT CONTRACT

This Software Maintenance Agreement (SMA) is between: Sapphire Solutions and Middleshire

University.

1. SUPPORT SERVICES: The nature of the Support Services rendered will include the

following activities:

a) Assist in Application Recovery in case of major system crash and database failure.

b) Assist in modification of application.

c) Bi-monthly routine maintenance of the system by Sapphire Solutions Technical team.

d) A well-documented manual on the software will be provided to Middleshire University to

ensure ease of use.


e) Trainings will be organized to assist staffs and students of Middleshire University to have a

clear understanding on how to make optimal use of the application.

2. TERMS OF AGREEMENT: This Agreement shall be effective when signed by both parties

and shall remain legal, for a period of 12 months subject to performance in accordance with the

obligations of the two parties.

Cost and Payment Plans:

Maintenance services will be at 10% of the total project cost annually.

100% payment must be made for support service activation.

A reminder for the annual support fee will be sent 30 days prior to the end of the free support

period.

The maintenance fee for subsequent years is subject to change (increase or decrease).

NB: Special/ additional services such as maintaining systems made by other companies will be billed

hourly depending on the complexity of the problem.

CONTRACT DURATION: This contract will begin one year after the software delivery date and

terminate exactly one year after if SMA contract is not renewed.

This service will be free for one year after deployment. Subsequently, a maintenance contract will be

agreed upon.

SUPPORT AND MAINTENACE PLAN APPROVAL

__________________________ _____________________

Middleshire representative Date


5/5/2014

Sapphire representative Date

PAYMENT

The payment should be made in three instalments, First instalment at the beginning of the project,

which is 30% of the total cost (£ 53,931.00) and the second instalment at the middle of the project

when the project has commenced, and is 30% also. The final payment should be done at the completion

of the project which is 40%.

APPROACH TO QUATITY ASSURANCE:

PURPOSE

The aim of this Software Quality Assurance (SQA) Plan is to outline the steps that would be taken to

obtain the optimal quality of the software system “Studynet”. It provides a standardized framework to

ensure quality throughout the project life cycle.

It clearly states the approach and methodology to software quality assurance that the development

personnel would adopt to provide the quality of the software.

SCOPE


This plan covers SQA activities throughout the requirements analysis, architecture and design,

implementation, testing and verification, and user acceptance phases of the development of “Studynet”.

The development team of Sapphire Solutions is responsible for adopting the procedures into the

development of the software.

PROJECT SUMMARY

There is high demand for more efficient and flexible Virtual Learning Environment (VLE) systems and

this project creates a VLE system “Studynet” using Moodle for Middleshire University.

The purpose of this application is to create a learning environment to manage activities of students and

lectures. The system helps to manage collaboration between students and lecturers and it would have

features like quiz, assignment submission, grading system, forum, plagiarism checker, etc.

REFERENCE DOCUMENTS

• IEEE STD 730-2002, IEEE Standard for Software Quality Assurance Plans.

MANAGEMENT

ORGANIZATION

The Quality Assurance Manager (QAM) leads the SQA team to to conform to the SQA plan and he/she

is assisted by a vice-QAM. They are also responsible to inform the customer or the top management if

they are problems with the software quality.

TASKS

The major responsibility of the SQA team is to monitor the procedures to verify if they are followed

accordingly and that standards are met. The SQA team also inspects whether all group members fulfills

the tasks in relation to the planned quality. The SQA team also arranges and attends internal reviews

and they also monitor consistency between different documents.

RESPONSIBILITIES

The Quality Assurance Manager (QAM) assigns tasks among the Software Quality Assurance (SQA)

team. Little problems can be solved by the team while bigger problems are to be reported to the Project


Manager (PM) through the QAM. Any problem must be reported to QM, the QM would communicate

to other external teams.

DOCUMENTATION

PURPOSE

This section will discuss the about the documentation of the project, validation and verification and

software maintenance. It is taking into account documents to be evaluated for acceptability. It also lists

out the corresponding audits for each corresponding document to confirm if it is satisfactory.

The documents to be delivered in the different levels follow standards and these are described in the

next section in the project and are listed in the next section.

STANDARDS, PRACTICES, CONVENTIONS AND METRICS

DOCUMENTATION STANDARDS

Different documents would be created during the course of the project and the SQA team would be

responsible to check that the documents adhere to standards and this would be done through constant

monitoring. All documents have to be approved by the author(s) and leaders of the responsible team

and a member of the SQA team. All documents must be written in English.

These standards apply to both electronic, printed versions and any other format.

DESIGN STANDARDS, CODING STANDARDS, COMMENT STANDARDS

“Studynet” is going to be developed using Moodle; an open source Virtual Learning Environment that

currently meets open and international standards

The international standards are:

An Open source initiative

IMS LTI Certified

SCORM-ADL compliant

Open Badges


SOFTWARE REVIEW

The SQA team inspects all project and documents to ensure they follow the document standards and

that team members complete their given tasks. The connection of one document to another is also

reviewed. Observation to check coding standards would also be done. Random checks are also carried

out.

TESTING

The testing strategy would consist of three (3) levels:

1) Integration Testing - this would involve testing several modules of the system and would also

test different parts of the system to ensure they work as a whole. Each test is used to check if the

system fulfills some specific criteria(s) in the requirements.

2) Acceptance Testing –Here, customers are invited to test the system to check if it meets the

requirements. Acceptance test are carried out using practical data using cases from the

requirements.

3) Regression Testing – The idea behind this type of testing is to find new bugs after a major

change has been implemented to the application. It can also be taken when a code that was

working before stops working. It would be carried out by the testing team.

CRITERIA FOR TEST COMPLETION

Regression Testing: finalized when:

o At least 90% of modules functions have been covered, including all modified modules,

o All part of the system is error free.

Integration Testing: finalized when:

o 100% of module interfaces have been tested.

Acceptance Testing: Complete when:

o The customer is satisfied that the product has met the agreed upon requirements.


PROBLEM REPORTING AND CORRECTIVE ACTIONS

It is necessary to solve any problem that occurs in the Configuration Item (CI). Some problem

includes:

Document problem:

Lack of conformance with other documents in the project.

Errors

Unfinished documents

Code problems:

Bad functionality

Lack of conformance to coding standards

Insufficient functionality

Method of problem reporting: It is the responsibility of whosoever discovers an error to report it to

the Project Manager and Quality Assurance Manager.

Method of solving problem: The team leader of a Configuration Item would solve the reported error.

When the problem is solved the SQA team is informed to check for correctness of the change.

Change in customer requirements: If the customer changes his requirements, the requested change

is checked to see if it complies with the User Requirement Document (URD). It is accepted if it

complies with the URD, but if it does not the team reaches a conclusion whether to accept the

changes or not.

TOOLS, TECHNIQUES AND METHODOLOGIES

The tools are selected based on what task it would perform in a project. It would be associated to

the project phase it would be used. The selection of these tools would be analyzed with the Quality

Assurance (QA) team.

Tool Name Purpose


Microsoft Office suite (i.e., Word, Excel

and PowerPoint)

General Documentation and excel would be

used to record defects

SkyDrive All materials are stored on Microsoft

SkyDrive

The techniques that would be used to ensure requirements are fully functional:

1) Peer review: here team members would review work on different sections and discuss this in

meetings to ensure all members understand how the system should would when fully

implemented.

2) Customer review: here the customer (could be a mentor) is requested to review the document,

could be as a user. The feedbacks are deliberated on and sent for final review.

3) Regression testing: this ensures all part of the system works well after testing and to make sure

new bugs won’t occur again.

SUPPLIER CONTROL

All external software (could be plugins) that have an untrustworthy source would be tested to check

if it meets standard while those that come from a trustworthy test would go through tests. The

programmers would decide whether they want to use this software and an agreement would be

made with other team members. All project members would have the software used for the

development of the application.

RECORDS COLLECTION, MAINTENANCE AND RETENTION

Minutes of meeting would be taken and documented. Meetings would be held twice a week. These

documents would be retained throughout the entire project.


TRAINING

The development team has developers well-grounded in PHP and Information technology

discipline. If there would be need for special training to update the developers skills, this would be

analyzed by the PM and QAM.

RISK MANAGEMENT

During the progression of the project, any risk that arises would be discussed with the PM and

action would be taken to effectively tackle the risk.

Glossary

Acronyms

CI Configuration Item

Customer Middleshire University

CM Configuration Manager

PM Project Manager

QAM Quality Assurance Manager

SCMP Software Configuration Management

Plan

SPMP Software Project Management Plan

SQA Software Quality Assurance

SRD Software Requirements Document

URD User Requirements Document

APPENDIX 1, SUPPLIER COMPANY OVERVIEW

Sapphire Solutions is an Information Technology Solution provider with its head office based in

Mauritius. Our company is specialized in state of the act website design / development, web portals, E-

learning solutions, Testing Solutions, Network solutions and Information Technology consultation.


Having in mind that we have to deliver a world class standard solution to our clients, Sapphire solution

staff is certified with Web developers, Network Administrators and project manager. Sapphire solution

is also a certified Microsoft Gold member and Oracle partner.

We offer the following services:

1. Server Management

2. Network Support

3. Network Security

4. IT Systems Management & Accounts

5. IT Planning & Review

6. Support, training

7. Server Backups

8. CCTV Installation

9. Cyber Security Consultancy

10. Software Development

11. Web site design and Development

TEAM MEMBERS AND ROLES


Nwabueze N Vitalis: Project manager in

Sapphire Solutions. A Microsoft certified

professional and an accredited software engineer

MORONKUMBI MUBARAK

Assistant Project Manager in Sapphire Solutions.

A project manager which years of hands on

experience

OKICHE MBANEFO EMMANUEL

Moodle Manager. A software developer with

years of experience


OKPALA OKWUDILI SAMUEL:

Database administrator A Sun Micro systems

certified developer and Open source

professional.

OKPALA EMEKA PRINCE

Quality Assurance Manager.

ODAH IRIPIA BENARD

Graphics Designer.

MUSTAPHA HALIRU BAKIIYA

Documentation Manager.

OPEMIPO KASSANDRA

Assistant Documentation Manager.


APPENDIX 11, REFERENCES OF PREVIOUS WORK

Below are previous projects done by Sapphire Solutions:

Caspio

An online database system designed for

Caspio Inc.

url: www.caspio.com

Project Start date: 9/10/2010

Project End date: 22/11/2010

http://www.caspio.com/


Southampton Solent University

Sapphire Solutions designed the official site

of Southampton Solent University.

url: www.solent.edu

Project start date: 10/5/2009

Project end date: 30/6/2009

Arik Air

http://www.solent.edu/


Sapphire Solutions upgraded the website of

Arik Air from html to html5, allowing ease

of use and carrying out of transactions easy.

url: www/arikair.com



Shepherd Software

This educational application for kids for

kids was designed by Sapphire Solutions.

url: www.shepherdsoftwares.com




APPENDIX III, ACCOUNT MANAGEMENT & CONTACT

Sapphire Solution’s Account Manager

Name: Miss. Yasmeen Muhammad Maccido.

Mobile: +2305848758

Email: [email protected]

.

mailto:[email protected]


AGREED MEETING PLAN, DATES AND TIME

Our meetings have been scheduled 2 times a week, every Wednesdays and Saturdays. This will enable

the team members understand and know the progress of the project.

TEAM GROUND RULES

Sapphire Solutions have rules guiding the conduct of its employees. The guidelines are as follows:

1. No nonchalant attitude in the office environment.

2. No slipshod in carrying out duties.

3. No late coming to meetings.

4. No dispute with colleagues.

Penalties have been set aside for any defaulter.

All staffs of Sapphire Solutions have agreed and signed to this rules.


APPENDIX IV, QUALITY ASSURANCE

The SQA team inspects all project and documents to ensure they follow the document standards and

that team members complete their given tasks. The connection of one document to another is also

reviewed. Observation to check coding standards would also be done. Random checks are also carried

out.

TESTING

The testing strategy would consist of three (3) levels:

1) Integration Testing - this would involve testing several modules of the system and would also

test different parts of the system to ensure they work as a whole. Each test is used to check if the

system fulfils some specific criteria(s) in the requirements.

2) Acceptance Testing –Here, customers are invited to test the system to check if it meets the

requirements. Acceptance test are carried out using practical data using cases from the

requirements.

3) Regression Testing – The idea behind this type of testing is to find new bugs after a major

change has been implemented to the application. It can also be taken when a code that was

working before stops working. It would be carried out by the testing team.

CRITERIA FOR TEST COMPLETION

Regression Testing: finalized when:

o At least 90% of modules functions have been covered, including all modified modules,

o All part of the system is error free.

Integration Testing: finalized when:

o 100% of module interfaces have been tested.

Acceptance Testing: Complete when:

o The customer is satisfied that the product has met the agreed upon requirements.


PROBLEM REPORTING AND CORRECTIVE ACTIONS

It is necessary to solve any problem that occurs in the Configuration Item (CI). Some problem

includes:

Document problem:

Lack of conformance with other documents in the project.

Errors

Unfinished documents

Code problems:

Bad functionality

Lack of conformance to coding standards

Insufficient functionality

Method of problem reporting: It is the responsibility of whosoever discovers an error to report it to

the Project Manager and Quality Assurance Manager.

Method of solving problem: The team leader of a Configuration Item would solve the reported error.

When the problem is solved the SQA team is informed to check for correctness of the change.

Change in customer requirements: If the customer changes his requirements, the requested change

is checked to see if it complies with the User Requirement Document (URD). It is accepted if it

complies with the URD, but if it does not the team reaches a conclusion whether to accept the

changes or not.


APPENDIX V, DETAILED SPECIFICATIONS OF THE PRODUCT

Functional Requirements

1 Content Management: functionality will manage and organize the module content. Learning

tools will be managed with this functionality.

2 Plagiarism Checker: This functionality will check for students’ report similarity index. It will

check online sources, other academic materials etc.

3 Grading Assignments: This will help lecturers grade the students based on the method they

desire.

4 Communication: This functionality will provide a social platform for students, lecturers, module

leaders and even prospective students. Communication will be through email or blogging or

feedback form.

5 Access based on Roles: System users can access the system because of this functionality. It will

restrict or grant access to a user based on his/her level of access.

6 Diary and Calendar: The system functionality can give users the privilege to view the date on

the application and also use it to create an event.

Non-Functional Requirements

1 Studynet’s interface must be attractive.

2 The system must work with minimal delay; the response time should be fast.

Front-End

My Middleshire – this is the web home page, linking to other pages.

Campuses – it shows information of different campuses.

Login – it allows users to put in their credentials to log into the system.

Learning – it contains learning information for students.

Support – it contains support information for the web page and application users.

Hardware Requirements


Laptop or Desktop running Windows, Linux or Macintosh Operating System, This systems must have

at least minimum of 50GB hard drive space, 2GHz processor, 2GB Random Access Memory, internet

connection and web browser (preferably Mozilla Firefox).

References Anon., n.d. [Online].

Anon., n.d. CIB Download Center. [Online]

Available at: http://cib.telecomit.gov.mu/English/Pages/Downloads/Downloads.aspx

[Accessed 29 April 2014].

Parker, D., Craig, M., & Craig, M. A. (2008). Managing Projects, Managing People. MacmillanEducation AU.

Wysocki, R. K. (2009). Effective Project Management: Traditional, Agile, Extreme. (5th ed). Indianapolis:

Wiley Publishing Inc.

Hughes, B. & Cotterell, M. (2009). Software Project Management. (5th ed). United Kingdom: McGraw-Hill

Education.

Sommerville, I. (2011). Software Engineering. (9th ed). United State of America: Addison-Wesley.