Revision History

Date Version Description Author

 Table of Contents
I. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.5 Overview
II. Project Overview
2.1 Project Purpose, Scope and Objectives
2.2 Assumptions and Constraints
2.3 Project Deliverables
2.4 Evolution of the Software Development Plan
III. Project Organization
3.1 Organizational Structure
3.2 Roles and Responsibilities
IV. Management Process
4.1 Project Estimates
4.2 Project Plan
4.2.1 Phase Plan
4.2.2 Iteration Objectives
4.2.4 Project Schedule
4.3 Iteration Plans
4.4 Project Monitoring and Control
4.4.1 Requirements Management Plan
4.4.2 Schedule Control Plan
4.4.3 Budget Control Plan
4.4.4 Quality Control Plan
4.4.5 Reporting Plan
V. Technical process plans
5.1 Development Case
5.2 Methods, Tools and Techniques
 I. INTRODUCTION

1.1. Purpose

The objective of this Software Development Plan is to define the

development activities in terms of the phases and iterations required for

implementing an enterprise application system to be used for the existing system

of Untouchably-Yummy Diner.

1.2. Scope

This Software Development Plan describes the overall plan to be used by

team Untouchaballs for developing the entire application system for Untouchably-

Yummy.

The plans as outlined in this document are based upon the estimated

product requirements defined by the team.

1.3. Definitions, Acronyms and Abbreviations

❖ Java – Computer Language commonly used in Object-oriented

programming

❖ Object-Oriented Programming - is a computer programming model that

organizes software design around data, or objects, rather than functions

and logic

❖ Windows, MACOS, Linux – Operating systems used to run in computers

❖ LAN – Local Area Network

❖ SDP – Software Development Plan

 ❖ UI – User Interface

❖ UX – User Experience

❖ IDE (Integrated Development Environment)- enables programmers to

consolidate the different aspects of writing a computer program.

❖ Cloud – or the internet

❖ Databases - a structured set of data held in a computer, especially one

that is accessible in various ways.

❖ Prototype – sample working project (not completely)

❖ Untouchably-Yummy – Company/ Small Business Diner name founded by

the CEO Marie Joy Morano-Sanchez

1.4. Overview

This Software Development Plan contains the following information:

❖ Project Overview – provides a description of the project’s purpose, scope

and objectives. It also defines the deliverables that the project is expected

to deliver.

❖ Project Organization – describes the organizational structure of the

project team.

❖ Management Process – explains the estimated cost and schedule,

defines the major phases and milestones for the project, and describes

how the project will be monitored.

❖ Technical Process Plans – provides an overview of the software

development process, including methods, tools and techniques to be

followed.

❖ Supporting Process Plans – this includes the configuration management

plan.
 II. PROJECT OVERVIEW

2.1. Project Purpose, Scope and Objectives

The application system project will only be implemented or applicable for the

current Untouchably-Yummy Diner business and implementing it to businesses that are

not in context with currents’ Untouchably-Yummy processes will disregard its purpose.

The application system proposed will only run through Desktop/ Laptop computers

with java installed and are locally connected in Diner’s LAN. Yet, it is protected and

secured through the help of implementing account authorization.

The use of Mac OS, Linux, or any other OS that are not Windows 7+ are not

compatible for the proposed project. Since the project is built in the current age, as a

skilled team, it is the best option to utilize the latest and much secured tools invented for

their intended purpose.

Accessing confidential files and information can only be done through local

connection with admin authorization. And other services such as delivery, will take place

online with limited connection based on the coverage of the small business.

The team will mainly use Java language and Netbeans-software for building the

proposed application system. The team believed that the IDE and language used is

suitable enough and covers all the essentials in pursuing the project.

The application system will consist of three User Interfaces, exclusively for the

delivery, counter, and for the manager.

2.2. Assumptions and Constraints

The use of Netbeans IDE requires some specifications for it to run and be

used the UI/UX Designer. With limited budget, providing a platform with an above

specification requirement as an asset will be a challenge for the team, and can only

provide with the minimum requirement. With that possible problem being known, as a

team we provide alternatives for the project to run smoothly even if that crisis comes and

it is to timely-backup the project.

2.3. Project Deliverables

The following deliverables will be produced during the project:

❖ Software Development Plan

❖ Vision

❖ Use Cases

❖ Glossary

❖ Software Architecture Document

❖ Design Model

❖ Implementation Subsystem

❖ Build

❖ Test Package

❖ Change Requests

❖ Test Summary

❖ Release Notes
2.4. Evolution of the Software Development Plan

The software development Plan will drastically change based on the timeframe

agreed upon stakeholders.

III. PROJECT ORGANIZATION

3.1. Organizational Structure

3.2. Roles and Responsibilities

Role Responsibility

Recipient for the proposal and guides the

CEO team for the pursuance of the proposed

application system project

Serves as the Scrum Master, and head

for the planning and production of the

Project Manager
project. Covers all aspect of the project

and compiles it in a mannerly way.

Primarily responsible for the Analysis &

Design and, Implementation disciplines

Software Engineer
for the application system project stick to

its rules set.

Implements the design and follows the

rules set by the software engineer.

UI/ UX Designer Responsible and defines the completion

of the proposed project meeting users’

expectations.