sp-assignment 1-ng beng han

Software Processes i Taylors Instant Notification System

ITS 60703

Software Process

Assignment 1 Hand out Date: 26

th March 2015 (Thursday)

Hand in Date: 17th

April 2015 (Friday by 6:00p.m.)

The assignment should be attempted in group of maximum 2 students

Complete this cover sheet and attach it to your assignment this should be your first page!

Student declaration:

I declare that:

I understand what is meant by plagiarism

The implication of plagiarism have been explained to us by our lecturer

This project is all our work and I have acknowledged any use of the published or

unpublished works of other people.

Name Student ID

1. Ng Beng Han 0319496

2. Liew Soon Hen 0315575

Avoid copy and paste job in your report and it is considered as plagiarism. Plagiarism in all

forms is forbidden. Students who submit plagiarized assignment will deserve a 0 marks.

Software Processes ii Taylors Instant Notification System

N & L Corporation

Learning without Limit

Taylors Instant Notification System

Software Processes

04/01/2015

Document Number: DINS 301

Contact Number: +6014 967 5367 (Mr. Ng) +6013 262 2168(Mr. Liew)

Software Processes iii Taylors Instant Notification System

Contents

Contents ........................................................................................................................ iii

Company Background .................................................................................................. v

Vision ........................................................................................................................ v

Mission Statement ..................................................................................................... v

Processes ...................................................................................................................... 6

Project Planning Process ........................................................................................... 6

Purpose ............................................................................................................................... 6

Inputs.................................................................................................................................. 6

Entry Criteria ..................................................................................................................... 6

Process Flow Diagram ....................................................................................................... 7

Tasks .................................................................................................................................. 8

Verification ........................................................................................................................ 9

Metrics ............................................................................................................................... 9

Exit Criteria ........................................................................................................................ 9

Outputs ............................................................................................................................. 10

Recruitment Process .................................................................................................. 11

Purpose ............................................................................................................................. 11

Inputs................................................................................................................................ 11

Entry Criteria ................................................................................................................... 11

Process Flow Diagram ..................................................................................................... 12

Tasks ................................................................................................................................ 13

Verification ...................................................................................................................... 14

Metrics ............................................................................................................................. 14

Exit Criteria ...................................................................................................................... 14

Outputs ............................................................................................................................. 15

Software Maintenance Process ............................................................................... 16

Purpose ............................................................................................................................. 16

Software Processes iv Taylors Instant Notification System

Inputs................................................................................................................................ 16

Entry Criteria ................................................................................................................... 16

Process Flow Diagram ..................................................................................................... 17

Tasks ................................................................................................................................ 18

Verification ...................................................................................................................... 19

Metrics ............................................................................................................................. 19

Exit Criteria ...................................................................................................................... 19

Outputs ............................................................................................................................. 20

Software Processes v Taylors Instant Notification System

Company Background

N&L Corporation started in year 2008, when the founders Liew Soon Hen and Ng

Beng Han noticed something minor which is wrong with the education system in Malaysia.

However, they noticed that this error, however minor, is affecting the general education

system in a large way in the long run.

In the last decade, technology has flown at a ridiculous rate. A lot of new

technological wonders and gadgets have been invented in the last decade. However, little or

none of these new technological discoveries has gone into education. Most entrepreneurs

focus on profits a lot more than students welfare. Liew and Ng has noticed that all these technological wonders can do miracles if implemented into a students life in his/her education.

Therefore, the company N&L is born with a passion of seeing the world receive a

better education from young, creating better leaders for our future and creating a better world

for our future generation.

Vision

The companys vision is to have all students in the world upgrade their quality of education by utilizing the technology available in the world right now.

Mission Statement

To develop applications to help students around the world maximize their learning

capabilities from their education

To reduce unnecessary hassle from a students life so that he/she may focus better on their education

N & L Co. Mobile Application

Software Processes 6 Taylors Instant Notification System

Processes

Project Planning Process

Purpose

To produce and communicate effective and workable project plans.

To determines the scope of the project management and technical activities

To identify the process outputs, project tasks and deliverables

To establish schedules for project task conduct.

To analyze the technologies and resources required to accomplish project tasks

Inputs

An approved project idea

Suitable technology to carry out the project

Entry Criteria

A proper team to be assembled

The company assigned this project



Process Flow Diagram



Tasks

T1. Define & Collect Project Requirement

Project Manager determine the requirements and collect them from the client

Document the requirement that has been recorded and classify them into two parts, functional and non-functional requirement

T2. Identify the scope and objectives of the project, consensus with the client to avoid misunderstanding

T3. Project Planning

Project Planner plans the flow of the project

Schedule the time to complete this tasks on time

Plans the process for this project according to the requirement that has been given

T4. Requirement Analysis

Analyze and specify the requirement of the project

Analyze and identify the risk that might occurred when undergo this project

Estimate, calculate and produce a project budget and show it to the client for confirmation

Analyze the resources and technologies available and needed to complete this project

Allocate the tasks to all the managers of the company and assign the responsibilities to them

Define the operating environment and software needed to achieve this project

Request Recruiting Manager to employ human resources which is required to achieve the project

T5. Document all the reports, plans and process templates and produce a proposal

T6. Execute the process that is planned if this project is approved by the client



Verification

V1. The requirement which is determined must be verified by the client and receive an approval to start the project planning

V2. The scope & objectives of the work for the project must be related to the requirement that has been verified

V3. The project schedule must be arranged in order to accomplish this project within the timeframe that has been given by the client

V4. Project processes that has been planned must be verify by the client and validated by ISO/IEEE standard

V5. Technologies, resources that are required, labor cost, revenue cost and the risk contingency plan cost must be taken into account for the project budget

V6. Project plans, reports and all the documentation must be verified by the Project Manager and approved by the client before any execution

Metrics

Accuracy of the project budget

Performance of the project plan

Exit Criteria

The resources required for the project is available, adequate and appropriate and that the timescales to completion is achievable.

The requirements for the project are clearly defined.

Proper authorization for the project has been obtained.



Outputs

The following deliverables are outputs of the test execution process:

D1. The scope and objectives of the work for the project is defined.

D2. Tasks and resources necessary to complete the work are sized and estimated

D3. A plan for the execution of the project is developed.

D4. A plan for the execution of the project is activated.

The following quality records are outputs of the system test execution process:

Required Record Custodian Retention Period

Requirement of the

project

Project Manager & Client The entire project

Scope & objectives of the

work for the process

Project Manager & Project

Planner

Until all the tasks of

the process has

been accomplished

Project Schedule Project Manager The entire project

Project Process & Reports Project Planner Until it is submitted

to and approved by

Project Manager

All the documentation of

this process

Project Manager For the next related

project that might

be assigned by the

company



Recruitment Process

Purpose

To provide the company with necessary human resources which are the mobile apps designers & programmers

To accomplish some tasks that cant be completed by the companys staff without the profession and expertise

To training & develop the designers and programmers who are selected and hired to work for the companys projects

Inputs

Project requirements

Job descriptions

Job qualification and requirements

Entry Criteria

Project planning process has been done

Project requirement has been analyzed and approved by the client

Received the approval to execute the project



Tasks

T1. Define Job Requirement

Project Manager define the job requirement to complete this project

Documentation of knowledge, skill, ability and other personal characteristics required for the job

Prepare the job description and job specification which is according to the project needs

T2. Sourcing

Recruiting Manager plans some sourcing strategies

Recruiting Manager do some research such as data mining and advertising job vacancy to attract experts and professional to apply for the job

Employ recruitment consultancies or agencies to find passive and potential candidates

T3. Recruiting Manager open job requisition

T4. Process of Applicants

Check and validate all the job applications, check whether the job application is filled completely

Process the applicants that has submitted a completed job application and rsums

T5. Screening & Selection

Screening rsums, job application and biographical information from the candidates

Schedule a job interview section for the applicants with recruiting manger so that recruiting manager could understand them more and recruit the right one

Filter all the potential candidates and run through a second interview which is ability and technique testing

T6. Recruiting Manager will hire the selected applicants and sent a confirmation letter to them by e-mail

T7. Recruiting Manager invite some experts to give more ideas and expose the technology available to the programmers and designers



Verification

V1. The job requirement for the job requisition is related to the requirement of the project

V2. Non-related job applicants are not found and apply for the job such as sales executive and accountant

V3. Job interview session must be scheduled with project manager and recruiting manager

V4. Skills and ability testing must be related to the job specification and verified by the Recruiting Manager and Project Manager

V5. Every recruits that have been selected by the recruiting manager must be also agreed by the project manager

Metrics

Abilities, technique, skills and performance of the recruits

Efficiency of the sourcing strategy

Number of applicants for the job

Exit Criteria

Every recruits can clearly recognize their role and responsibilities

Sufficient & potential recruits are hired to accomplish the project

Recruits are trained and developed, also, can cope well with the companys environment and accepted the way to accomplish the project



Outputs


D1. Skills required by the projects are identified

D2. Necessary human resources are provided for the project

D3. Skills and ability of personnel are developed



Job description & job

specification

Project Manager Until the recruiting

manager recruits all the

necessary human resources

Rsums, Job

Application

Recruiting Manager The entire process

Sourcing Strategy Recruiting Manager For the next recruitment



Software Maintenance Process

Purpose

To provide cost-effective support to a delivered software product

To plan for the software modification and operational support

To resolve the problems that reported by the user by using the methods available

Inputs

Problems that is complained by the users

Defects that is found by the developers

Solution for the reported problems

New requirement has been given by the client

Entry Criteria

Implementation of the software product has been undergone

Request for maintenance has been approved by the client



Tasks

T1. Users will give feedback and report some problems that they faced when using the software product

T2. Operation Manager collect the feedback and reported problems

T3. Classify the suggestion and reported problems into two parts, whether its an algorithm problems or the GUI of the mobile app.

T4. Request for the software product modification approval from the client

T5. Planning & Analysis

T6. Identify the level of disturb of the problems that affected the mobile app

Prepare a software maintenance plan, list down all the problems that have to be solved and new features that are required by the client

Operation Manager conduct a meeting with Project Manager and developer to discuss the reported problems and decide the modification

Analyze the problems in different perspective and figure out the resolution for every problems

Analyze the need of implementing new features or the suggestion that has been given by the users

T7. Developer develop and design the system and GUI of the mobile apps according to the problem resolution and the technologies available (install the new features

into the mobile apps if there is any)

T8. Document the problem resolution in the knowledge database

T9. Perform testing by the developer, ensure the problems have been solved

T10. Version Control Manager will identify the version of this new patch

T11. Operation Manager will pick some users, to run through an user acceptance testing

T12. Schedule a meeting with client to present the new patch of the software product with prototype and user manual

T13. Collect the feedback from the department and request to release this patch

T14. Release the patch if approved by the client

T15. Notify the users to update the software product, list down the details and changes of the new patch and show it to the user when they open the software

product



Verification

V1. Every reported problems has solutions to fix the defect

V2. Database has a record for all the reported problems and feedback

V3. Maintenance decision has been approved by the company and client

V4. Update patch of the mobile app has been tested by the developer and users

Metrics

Backlog

Exit Criteria

A completed software has been developed

Testing has been undergo by the developer and users

Mobile app can function in a good condition and receive approval for implementation



Outputs


D1. Solution for the reported problems

D2. Maintenance Approval

D3. Prototype with the latest patch for testing

D4. An update patch for the mobile app



Feedbacks & Reported

Problems

Manager Starting until the

mobile app has

been developed

Problem Resolution Manager Until it has been

register in the

knowledge database

Maintenance approval

letter

Manager After approved by

the company

Prototype after the

patching

Manager & Developer From the design

process until

acceptance testing


Software Process Improvement Plan 21 Taylors Instant Notification System

N & L Corporation

Learning without Limit


Software Process Improvement Plan

04/01/2015

Document Number: DINS 301

Contact Number: +6014 967 5367 (Mr. Ng) +6013 262 2168(Mr. Liew)



Contents

Introduction ................................................................................................................. 23

Overview ...................................................................................................................... 23

Assumptions/Constraints/Risks ................................................................................ 24

Assumptions ............................................................................................................ 24

Constraints ............................................................................................................... 24

Risks ...................................................................................................................... 24

Process Review Background ..................................................................................... 25

Process Review Methodologys ................................................................................ 25

Process Review Findings and Recommendations ................................................... 25

SPI Approach ............................................................................................................... 26

Goals ..................................................................................................................... 26

Methodology ............................................................................................................ 27

Roles and Responsibilities ......................................................................................... 28

Acronyms ..................................................................................................................... 29

Bibliography ................................................................................................................ 30

Record of Changes ..................................................................................................... 31

Approvals ..................................................................................................................... 32



Introduction

This Software Process Improvement Plan (SPIP) describes the approach for continued

software development process improvement during the life cycle of the Taylors INS. The document identifies the specific actions that will be taken to improve the software process, and

outlines the plans for implementing those actions.

This document is intended for developers, testers, and the client, which is Taylors University. This document will start with the overview of this document, assumptions,

constraints and risks, and will detail the process review and SPI approach for the process.

The process that this document will discuss and improve is the project planning process.

Overview

Nowadays, students are unable to manage their time wisely. A students life does not just revolve around assignments. A students life is also all about joining clubs and societies and meeting new friends and working with them. But sometimes, when a student gets too distracted

by his social life, he tends to forget about his assignments and projects that he should have done

earlier.

In this decade, technology has grown very rapidly and now almost everyone has their own

smartphone. Therefore, N&L Corporation has decided to create a mobile application that brings

a lot of benefits to the students. The company has collaborated with Taylors University to make this project a success.

This application, named the Taylors INS (Instant Notification System), serves to bring information and convenience to the students and lecturers in Taylors University. To make Taylors INS a success, the company has come up with 3 processes, the recruitment process, project planning process and risk management process.



Assumptions/Constraints/Risks

Assumptions

In the project planning process, analysis is done of the proposed project plan. After the

analysis, the project plan will then be documented and then executed. The team assumes that an

analysis of the proposed plan alone does not properly ensure that the plan can be executed

perfectly and with minimal risk.

Constraints

The team may not have enough human resources to carry out any additional steps in this

SPIP. The team has already allocated a lot of human resources to carry out the analysis of the

plans and may not be able to afford transferring staff to carrying out the feasibility studies.

The team may also not have the technology or expertise to properly carry out these

additional steps and may cause the new improved process to produce worse results than before.

The team will need to hire additional specialized staff to carry out the feasibility studies.

Risks

Without the implementation of this SPIP, the project planning process risks a plummet in

quality of the plans proposed. The proposed plan may not be up to standard and may cause

unwanted incidents to occur in the life cycle of Taylors INS. The plans produced may be financially sound and risk-minimized, but they may not be feasible technically and operationally.

The analysis of the plan coupled with the feasibility studies will ensure that the plans produced

by this process is stronger and will be able to be implemented safely.



Process Review Background

To make this project a success, the team has implemented 3 processes, the recruitment

process, the software maintenance process and the project planning process. To ensure that all 3

processes run smoothly, process reviews are carried out routinely. During a routine process

review, it was found that the project planning process is not perfectly as efficiently as expected.

It was found that the plans produced from the project planning process is weak and is

often unable to be implemented effectively. Although all plans is run through an analysis in the

project planning process, it was found that the plans produced lacks technicality and operational

studies.

Process Review Methodology

The process review is done using the Kaizen process, which is a process meant for

continuous and incremental self-improvement that has been applied for businesses and

management. This method focuses on teamwork, quality circles and communications to facilitate

suggestions for improvement.

More specifically, the process review uses the Gemba Kaizen method. In the project

planning process, there is multiple sub-processes that occur, such as the analysis, documentation

and requirements gathering. Teams from each sub-processes will identify wastes, inefficiencies

and underused resources and to suggest improvements to the process as a whole.

The teams from different sub-processes will have meetings at regular intervals to discuss

areas of improvement. Encountered problems will then be discussed to find a solution.

Process Review Findings and Recommendations

During the process review, it was determined that just an analysis of the plans made in

the process was not enough to ensure the quality of the plans. The analysis involves analyzing

the project budget, resources and staffing, and the risk plan for the plans made. The analyzing

process ensures that the plan has enough preparation to make it run smoothly. However, this

analysis does not ensure that the plans are truly feasible in the real working environment.

The process review team has made recommendations to create an additional step after the

plans analysis to make sure that the plans are of quality and feasible in the industry. The process

review team suggests to study the technical and operational feasibility of the plans made. The

process review team strongly believes that these feasibility studies will really significantly

improve the strength of the plans.

Once a technical feasibility and operational feasibility study has been made, it will be a

lot easier to detect problems in the plans before they are executed and documented. The plans

will be made safe to execute and guaranteed to succeed technically and operationally.



SPI Approach

The process review team has suggested that feasibility studies should be done right after

the analysis sub-process in the project planning process. The feasibility study should make the

plans a lot more stronger and can be implemented more effectively.

The feasibility studies should include both technical and operational feasibility. These

studies should be carried out right after the analysis of the plans. Preparations for this new sub-

process will have to be made before this sub-process can be put into place. Additional human

resources will need to be allocated. Experts will need to be hired to advise and to help out. Staff

will need to be trained in this new sub-process.

Once the preparations are complete, this sub-process will be implemented into the

process immediately and without delay.

Goals

Project plans to be produced from this process that can be implemented into the company seamlessly and effectively. Proper analysis and proper feasibility studies will be carried

out and the plan will be both strong and feasible to be implemented in the company. This

will satisfy the process review teams suggestion of implementing a feasibility study after the analysis process.



Methodology

To initiate this process improvement, the team needs to allocate human resources to carry

out the feasibility studies. The team will also need to train the staff to be able to carry out the

feasibility studies effectively. Schedule adjustments will also have to be made for the whole

project planning process.

Once training is done and the staff is ready to carry out the feasibility studies, it will be

implemented into the project planning process directly after the analysis sub-process.

The team will be measuring the effectiveness of this new implementation by measuring

the number of defects in the plans produced by this process. The effectiveness can also be

measured in process reviews of the process that will be held continuously in its first year of the

implementation.

Once the feasibility studies sub-process has been implemented, continuous monitoring

and control will be maintained by conducting several more process reviews on this process over

the next year. After each process review, the number of defects and complains the process

receives will be reduced drastically. At the end of the review year, project plans produced should

be strong and the quality significantly improved.

After every process review, proper reports will be completed and sent to the stakeholders and

the management for their perusal. For every subsequent report to be sent, the version of the

document will be incremented so that the changes can be made obvious to the readers.

Improvements to the process will also be detailed in the new version of the report.



Roles and Responsibilities

Role Responsibility

Project Manager Determine and collect the requirements of the

project from the client

Consensus with projects client

Document the requirements and pass it down

to Project Planner

Project Planner Receive the requirements of the project

Plan the processes that will be needed for the

project

Prepare a project plan and project schedule

Recruiting Manager Recruits the human resources that is required

for the project

Operation Manager Manage the issues of the software product

Version Control Manager Control the version of the software product

Table 1 - Roles & Responsibilities



Acronyms

Acronym Literal Translation

CMMI

Capability Maturity Model Integration

CMS Centers for Medicare & Medicaid Services

INS Instant Notification System

N&L Co. Ng & Liew Corporation

PDCA Plan-Do-Check-Act

PMP Project Management Plan

SCAMPISM

Standard CMMI Appraisal Method for Process Improvement

SDMP System Development Management Plan

SPI Software Process Improvement

SPIP Software Process Improvement Plan

Table 1: Acronyms



Bibliography

Anderson, D. (2009, July 24). Recruiting Process Flow Map. Retrieved from Slide Share:

http://www.slideshare.net/stixnpucks/recruiting-process-flow-map

Recruitment Process. (n.d.). Retrieved April 1, 2015, from Seven Step RPO:

http://www.sevensteprpo.com/recruitment-process

Sbair, Z. (2011, July 24). Human Resource Management Process. Retrieved from Slide Share:

http://www.slideshare.net/ZeeshanSabir/human-resource-management-process

team, M. (n.d.). Processes in Human Resource Management. Retrieved from Management Study

Guide: http://www.managementstudyguide.com/processes-in-human-resource-

management.htm

The Recruitment Process. (n.d.). Retrieved August 5, 2012, from Acas:

http://www.acas.org.uk/index.aspx?articleid=748



Record of Changes

Version

Number Date Author/Owner Description of Change

1.0 4/4/2015 Ng Beng Han

Liew Soon Hen

Changes of Project Planning Process

Table 4: Record of Changes



Approvals

The undersigned acknowledge that they have reviewed the Software Process Improvement Plan

and agree with the information presented within this document. Changes to this Software Process

Improvement Plan will be coordinated with, and approved by, the undersigned, or their

designated representatives.

Signature: Date:

Print Name:

Title:

Role: Submitting Organizations Approving Authority

Signature: Date:

Print Name:

Title:

Role: CMS Approving Authority

Signature: Date:

Print Name:

Title:

Role: CMS Business Owner

Software Process Improvement Plan Error! No text of specified style in document. 0


URL of the Project

http://benghann.wix.com/instaylors

sp-assignment 1-ng beng han

Documents

software process assignment

liew software processes

plagiarized assignment

recruitment process

implication of plagiarism

project planning process

process flow diagram

document number