Problems Encountered During Software Development

Problems

• Poor requirements – if the requirements are not clear, unfinished, too common, and not testable, then there will be problems.

• Unrealistic schedule – if too much work is given in too little time, problems are inevitable.

• Inadequate testing – no one will know whether or not the program is any good until the customer complain or systems collide.

• Futurities – requests to pile on new features after development is underway; extremely common.

• Miscommunication – if developers do not know what’s needed or customer’s have wrong expectations, problems are assured.

Solutions

• Solid requirements – clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players.

• Realistic schedules – allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.

• Adequate testing – start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing.

• Stick to initial requirements as much as possible – be prepared to defend against excessive changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes.

• Communication – require walkthroughs and inspections when appropriate.

Progress Comparation with the Gantt Chart

 

 

The above chart shows what we are planning a project early in project development. However plans have been arranged to have some differences with the way the project is now but the step that are shows in gantt chart have been followed. For example, now we have to finished the task to build the database but we didn't do the task anymore. so what was planned in gantt chart will be changed according by this progress project.

therefore, we hope our project will be complete on time, although our early plan is no same with our progress project.

Software Requirement Specification (SRS)

SRS is a complete description of a system to be developed. Includes use cases which also known as functional requirements. SRS also contains non - functional requirements which impose constraints on the design or implementation.

Car Accessories Inventory System

Purpose 

The objective of this SRS document is to define the activities for the Car Accessories Inventory System which is using web based application in terms of its iterations, requirements, specification and flow required during the phases of its development.

Scope

Car Accessories Inventory System is an offline application that allows user to update their own financial, marketing, database and item stock according to their daily, monthly and yearly business.

Objective

 To reduce the difficulties in handling any stock in the shop and to increase the use of computers in business management.

Functional Requirements

System Environment

Use Case Diagram

Functional Requirement Specification

Login

Description

This use case allows the administrator such as accounting staff and marketing staff   to enter into the system by entering their username and password as provided. Besides that, the administrator that forgot their password can enter the reset password process to get their new password to login. 

 Manage Financial

Description

This use case allows the accounting to update all data for car accessories shop for daily, monthly n yearly financial.

Manage Stock

Description

This use case allows the accounting to manage stock for their item that whether they want to order the new product or update the current stock.

Maintain Product Catalog

 

Description

This use case allows the marketing staff to make the new idea of promotion catalog for print and distribute it for customer.

Setup Promotion

Description

This use case allows the marketing staff to setup promotion for this car accessories shop. The marketing will provide idea to do the promotion such as banner or advertisement.

Manage Item

 

Description

This use case allows the vendor to deliver or collect back the order.

Actors of The System

Non Functional Requirements 

Security

Employee and management are required to login before using the system.

- Require Login

Each employee and management must have their own id to login in the system.

Flexibility

The system that being used is capable of being change and update.

Performance

The performance of the system is good because the system is running on high end device.

- Device

The system is using a computer with Intel i7 Processor and running on 2 GB RAM.

Usability

This system can be used by employee and management without any difficulties.

Reliability

This system can perform and maintain its functions in routine circumstances without any major error.

Software Design Document (SDD) Template

Software Design Document or SDD shows how the software system will be structured to satisfy the requirements. It is the primary reference for code development and, therefore, it must contain all the information required by a programmer to write code. The SDD is performed in two stages. The first is a preliminary design in which the overall system architecture and data architecture is defined. In the second stage, i.e. the detailed design stage, more detailed data structures are defined and algorithms are developed for the defined architecture.


TEMPLATE CONTENTS

1. Introduction
    1.1 Purpose
    1.2 Scope
    1.3 Overview
    1.4 Reference Material
    1.5 Definitions and Acronyms

2. System Overview


3. System Architecture
    3.1 Architectural Design
    3.2 Decomposition Description
    3.3 Design Rationale

   
4. Data Design
   4.1 Data Description
   4.2 Data Dictionary

5. Component Design

6. Human Interface Design
   6.1 Overview Of User Interface
   6.2 Screen Images
   6.3 Screen Objects and Actions

7. Requirements Matrix

8. Appendices

Requirement Analysis an Inventory System Problem

Hospital Muar provides medicines to patients and there are also 10 Klink Desa in Muar that receive supplies from Hospital Muar. XY Pharmacy supplies the medicine and delivers it to Hospital Muar and to the 10 Klinik Desa.

When ordering , Klinik Desa has to order through Hospital Muar for authority processes. The supplier will deliver the supplies directly to Klinik Desa but they often has the problem of receiving less than they ordered through Hospital Muar.

The procedure involved in the process is Klinik Desa will order from XY Pharmacy but it have to go through Hospital Muar for authorization. But , Hospital Muar can order straight from the supplier that is XY Pharmacy. In the process of ordering , Klinik Desa will send purchasing order form to Hospital Muar and the hospital will check the form and approve the purchasing order. After the purchasing order have been approved , the purchasing order form will be send to the supplier which is XY Pharmacy.

Then XY Pharmacy will send the invoice to Hospital Muar and Klinik Desa. XY Pharmacy then will send delivery note to both Klinik Desa and Hospital Muar. After a right amount of time , the supplies will be send to both Klinik Desa and Hospital Muar and the receipt will be given upon receiving the suppplies.

The technology and solution that we will be using is to develop the procedures using online systems. Compared to the old systems that using forms as a media to communicate that is to order , get authorization , delivery note and receipt , the new systems will also be using the form but the form is in the online based. For example if Klinik Desa want to order supplies they just have to login to XY Pharmacy page and key in what supplies they need but first they have to get confirmation from Hospital Muar and to get confirmation they have to go to Hospital Muar page and write down the supplies they need and the hospital will send confirmation to them. After that they can continue to order from XY Pharmacy and the cycle is repeated if they want to order new supplies.

To order medicine from the supplier, which is XY Pharmacy Klinik Desa and Hospital Muar can just using an order form that can be obtained at XY Pharmacy website. For Hospital Muar they can just order the supplies of medicine they need but Klinik Desa have to get confirmation from Hospital Muar first before they can proceed to order the medicine supplies. Both of this customer can just simply go to XY Pharmacy website and order the medicine supplies they need without going to XY Pharmacy to order. This will save both the customer and supplier time that they can use to do or concentrate on other things.

To keep track of the inventory, all of the entities such as Hospital Muar, Klinik Desa and XY Pharmacy will have to use or develop a software that can save, record , delete and update every supplies of medicine and other things that being ordered or sent. This software will record and save every log or every details about what is going on and what will be happen from time to time. By doing this alot of problems can be avoided such as tracing back missing item, retracing back what is the problem, and also can make the inventory system more neat and tidy and also can avoid errors or mistakes.

The database that we used to record the information is Microsoft Access.

The methodology that being used is prototyping methodology. This because the system is using a web based development and by using this methodology we can test the system for a while and if there is an error occured , we can throw away the previous design and start with a new and better design and functions.
By using this methodology we can also save a considerable amount of time by reducing re-work as the users see the product for the first time.

User Interface Draft 

This is a login form for our system and this form is used by all 3 entities that is XY Pharmacy , Hospital Muar and Klinik Desa.

 

This is an order form for our system that is used to order the supplies of medicine. This form is used by Klinik Desa and Hospital Muar.

 

This is an supply form that being used in our system and this form is used by supplier that is XY Pharmacy.

This is the database for Hospital Muar that being used to store imformation of the medicine , the description of the medicine, the date of the medicine arrived in the hospital and the quantity of stock.

 

This is the database for Klinik Desa and is used to store information about the medicine, the description of the medicine, and the quantity of stock.

 

This is the database for XY Pharmacy and is used to store medicine information, description of medicine and quantity of medicine stock.

Gantt Chart

 

This is the gannt chart of our project from that will take approximately about 80 days to complete and consist of several steps such as discussing the topic, creating the blog, following the project flow, analyzing the problem, designing the application interface, building interface and database, linking the coding with database and completing the coding, submitting the final report and lastly the final presentation.

Project Overview

Our project consist or our main focus of this project is to develop an inventory system of a small organization of our choice and our group choose a car accessories company as the organization and we will be studying their inventory system. We will try to understand more of what their company sell or supplies to their customer and we will try to improve or upgrade their system so it will be better and efficient. By combining our group main focus and the group name we named our project as Pioneer Car Accessories.

The mission of our project is to build a system where the supply of goods and the stock management will run properly and smoothly.

The objective of this project is to improve the quality of goods that being sold in the shops. Furthermore we also try to reduce the difficulties in handling any stock in the shop. Lastly we also want to increase the use of computers in business management.


The scope of our project is intended to be carried out regularly to conduct business using a system built so that work can be carried out with ease. Our approach to inventory is one of the examples of industry operations management. This system consists of suppliers, warehouses and customers.

Group Members Introduction

Our group name is Pioneer.

The group leader is Nurul Shazani Binti Sahidan from Gurun, Kedah. She have finish her diploma in Computer Science (Information Technology) at UTMKL. She have various of programming skills such as Java, C++, C, Visual Basic, and HTML.

The other group member is Mohamad Izzuddin Bin Mohd Rezmi from Petaling Jaya, Selangor. He also have finish his diploma in Computer Science (Information Technology) at UTMKL. His programming skills included  Java, C++, C, Visual Basic, PHP, and HTML.

The last member of our group is Mohd Syafiq Bin Sulaiman from Johor Bahru, Johor. He also have finish his diploma in Computer Science (Information Technology) at UTMKL. His programming skills included Java, C++, C, Visual Basic, and HTML.