The Technical Specifications And Production Plan

Published Date: 02 Nov 2017

The waterfall model is the initial method of structured system development. It is so named because it employs an ascending/descending approach. Although it has been criticized in recent years for being too rigid and unrealistic when it comes to rapidly meeting customer’s needs , the Waterfall Model is still widely used. It is attributed with providing the theoretical basis for other process models , to be introduced and followed widely in software engineering to guarantee the success of the project because it most closely resembles a "common" model for software development. In the waterfall approach, the whole process of software development is divided into separate phases.

The phases in the model are:

System Conceptualization. It refers to the consideration of all aspects of the targeted business utility or process, with the goals of determining how each of those aspects relates with one another, and which aspects will be integrated into the system.

System Analysis. This step refers to the gathering of system requirements, with the objective of determining how these requirements will be accommodated in the system. Extensive communication between the customer and the developer is vital.

System Design. Once the requirements have been collected and analyzed, it is necessary to identify in detail how the system will be constructed to perform necessary tasks. More specifically, the system design phase is focused on the data requirements (which information will be processed in the system), the software construction (how will the application be constructed), and the interface construction (what will the system look like / what standards will be followed).

Coding. Also known as programming, this step involves the creation of the system software. Requirements and systems specifications from the system design step are translated into machine readable computer code.

Testing. As the software is created and added to the developing system, testing is performed to ensure that it is working correctly and efficiently. Testing is generally focused on two areas: internal efficiency and external effectiveness. The goal of external effectiveness testing is to verify that the software is functioning according to the system design , and that it is performing all necessary functions or sub-functions. The goal of internal testing is to make sure that the computer code is efficient, standardized, and well documented. Testing can be a labour-intensive process, due to its iterative nature.

All these phases cascade to each other so that the second phase is started as and when a defined set of goals are achieved for first phase and it is signed off. All the methods and processes undertaken in the model are more visible.

Although the waterfall model has been used extensively over the years in the production of many quality systems, it is not entirely flawless. The basic demerits associated with the waterfall model are :

Real projects rarely follow the sequential flow that the model proposes.

At the beginning of the most projects, there is often a great deal of uncertainty about requirements and goals, and it is therefore difficult for customers to identify these criteria on a detailed level. The model does not accommodate this natural uncertainty very well.

Developing a system using the waterfall model can be an extensive, painstaking process that does not yield a working version of the system until late in the development.

Ans. 1.1 b) Few people in the modern computing world would use a strict waterfall model for their systems development life cycle (SDLC) as many modern methodologies have superseded this thinking. Models like the spiral model, joint application development, rapid iteration, code-and-fix , agile manifesto ,extreme programming etc.

The spiral model, for example, was designed to include the best features from the waterfall and prototyping models, and introduces a new component - risk-assessment. It is one of the best examples of a lifecycle model without a specific structure. The term "spiral" is used to describe the process that is followed as the development of the system takes place. An initial version of the system is developed, and then frequently modified based on input received from customer evaluations. Unlike the prototyping model, however, the development of each version of the system is cautiously designed using the steps involved in the waterfall model. With each iteration around the spiral (beginning at the centre and working outward), progressively more complete versions of the system are built. Risk assessment is included as a step in the development process as a means of evaluating each adaptation of the system to determine whether or not development should continue. If the customer decides that any identified risks are too great, the project may be halted. If a substantial increase in cost or project completion time is identified during one phase of risk assessment, the customer or the developer may decide that it does not make sense to proceed with the project, since the increased cost or lengthened time frame may make continuation of the project impractical or unfeasible. Due to the relative newness of the spiral model, it is complicated to assess its strengths and weaknesses. However, the risk assessment component of the spiral model provides both developers and customers with a measuring tool that earlier process models do not have. The measurement of risk is a feature that occurs everyday in real-life situations, but (unfortunately) not as often in the system development industry. The practical nature of this tool helps to make the spiral model a more realistic process model than some of its predecessors.

Ans. 1.2 a) A software development process, also known as a software development life cycle (SDLC), is a structure imposed on the development of a software product. It is often considered as a subset of system development life cycle. There are several models for such processes, each describing approaches to a variety of activities taking place during the process. A SDLC is a set of activities together with an ordering relationship between activities ,performed in a manner that satisfies the ordering relationship and produce the desired product at the same time. It is an abstract representation of a development process , which is to produce high quality software, therefore, the sequence of activities that will produce such a software.

The set of processes, activities and tasks can be adapted according to the software project. These processes are classified in three types: basic, for support and organizational. The basic processes are instantiated according to the situation. The support and organizational processes must exist independently of the organization and the project being executed.

The standard has the main intention of supplying a general structure so that the buyers, suppliers, developers, maintainers, operators, managers and technicians involved with the software development use a common language. This general language is recognized in the form of well defined processes. The structure of the standard is anticipated to be conceived in a flexible, modular way so as to be adaptable to the necessities of whoever uses it. The standard is based on two basic principles: modularity and responsibility. 

The principal lifecycle processes contain the core processes involved in creating a software product. The evolution of system development Process Models has reflected the changing needs of computer customers. As customers demanded quicker results, more involvement in the development process, and the addition of measures to determine risks and effectiveness, the methods for developing systems transformed. In addition, the software and hardware tools used in the industry changed -and continue to change- substantially. Quicker networks and hardware supported the use of smarter and faster operating systems that paved the way for new languages and databases, and applications that were far more potent than any predecessors. Numerous changes in the system development environment simultaneously spawned the development of more practical new Process Models and the demise of older models that are no longer functional.

Ans. 1.2 b) The software which I would prefer for university work , would have to be the prototyping model (keeping in mind its variations). The prototyping model was developed on the hypothesis that it is often complex to know all of the requirements at the beginning of a project. The prototyping model allows for these conditions, and offers a development approach that yields results without first requiring all information up-front which makes it ideal for a university’s level of work. Usually, users know many of the objectives that they wish to address with a system, but they do not know all the fine distinctions of the data, nor do they know the particulars of the system characteristics and capabilities.

There are a few different approaches that may be followed when using the prototyping model- creation of the major user interfaces without any substantive coding in the background in order to give the users a "sense" for what the system will look like, development of an abbreviated version of the system that performs a limited subset of functions; development of a paper system (depicting proposed screens, reports, relationships etc.), or use of an existing system or system components to demonstrate some functions that will be included in the developed system.

The various aspects of Prototyping are:

• Requirements Definition/Collection. It is similar to the conceptualization phase of the waterfall model, but not as comprehensive. The information collected is usually limited to a subset of the complete system requirements.

• Design. Once the initial layer of requirements information is collected, or new information is gathered, it is rapidly integrated into a new or existing design so that it may be folded into the prototype.

• Prototype Creation/Modification. The information from the design is rapidly rolled into a prototype. This may mean the creation/modification of paper information, new coding, or modifications to existing coding.

• Assessment. The prototype is presented to the customer for review. Comments and suggestions are collected from the customer.

• Prototype Refinement. Information collected from the customer is digested and the prototype is refined. The developer revises the prototype to make it more effective and efficient.

• System Implementation. In most cases, the system is rewritten once requirements are understood. Sometimes, the Iterative process eventually produces a working system that can be the cornerstone for the fully functional system.

Problems associated with the prototyping model, like other methods, prototyping is also having the following problems:

• Prototyping might lead to false expectations. Prototyping often creates a situation where the customer mistakenly believes that the system is "finished" when in fact it is not. More specifically, when using the prototyping model, the pre-implementation versions of a system are really nothing more than one-dimensional structures. The necessary, behind the-scenes work such as database normalization, documentation, testing, and reviews for efficiency have not been done. Thus the necessary underpinnings for the system are not in place.

• Prototyping might lead to badly designed systems. Because the primary goal of prototyping is rapid development, the design of the system can sometimes suffer because the system is built in a series of "layers" without a global consideration of the integration of all other components.

The combination of all the features of the Prototyping model with the its upper hand in speed, user interaction and more , is the basis behind choosing it as an appropriate model for university work , with the consideration of both its pros and cons.

----------------------------------------------------------------------------------------------------------------

Ans. 2.1) In its simplest figure, a feasibility study represents a definition of a problem or opportunity to be studied, an analysis of the current mode of operation, a definition of requirements, an evaluation of alternatives, and an agreed upon course of action. The activities for preparing a feasibility study are broad in nature and can be applied to any type of project, be it for systems and software development, making an acquisition, or any further projects.

There are mainly six parts to any effective feasibility study:

a. PROJECT SCOPE - which is used to define the business problem and/or opportunity to be addressed. The scope should be definitive and to the point; long-winded narrative serves no purpose and can actually perplex project participants.

b. CURRENT ANALYSIS - is used to define and understand the current method of implementation, such as a system. From this analysis, it is not uncommon to discover there is actually nothing wrong with the current system other than some misunderstandings regarding it or perhaps it needs some simple modifications as opposed to a major overhaul. Also, the strengths and weaknesses of the current approach are identified (pros and cons). In addition, there may very well be elements of the current system or product that may be used in its successor thus saving time and money later on. Without such analysis, this may never be exposed.

c. APPROACH - represents the recommended solution or course of action to satisfy the requirements. Various alternatives are considered along with details as to why the preferred solution was selected. In terms of design related projects, it is here where whole rough designs (e.g., "renderings") are developed in order to determine viability. A thorough analysis here is needed in order to perform the next step.

d. REQUIREMENTS - how requirements are defined depends on the object of the project's attention. Each exhibits totally different properties and, as such, are defined differently. Identifying requirements for software is also substantially dissimilar than defining them for systems.

e. EVALUATION - examines the cost efficiency of the approach selected. This begins with an analysis of the estimated full cost of the project. Additionally to the recommended solution, other alternatives are estimated in order to offer an economic comparison.

f. REVIEW - all of the previous fundamentals are then assembled into a feasibility study and a formal review is conducted with all parties involved. The review serves two purposes: to substantiate the thoroughness and precision of the feasibility study, and to make a project decision; either approve it, reject it, or ask that it be revised before making a final decision.

When to use a feasibility study: What was just described is essentially the same process followed when purchasing an automobile or a home. As the scope of the project grows, it becomes more vital to document the feasibility study particularly if large amounts of money are involved and/or the criticality of the delivery. Not only should the feasibility study contain sufficient detail to carry on to the next succeeding phase in the project, but it should also be used for relative analysis when preparing the final project review which analyzes what was delivered versus what was proposed in the feasibility study. Feasibility studies symbolize a common sense approach to planning.

Ans. 2.2) Planning to start a business such as a garment shop has its natural constrains like every other business out there. So, naturally , the impact of each feasibility criteria needs to be assessed in order to begin successfully , such as legal , technical and organizational constrains involved in this industry in particular.

Legal and Political Factors: A number of legal and political macro environmental factors affect small businesses in the clothing industry. The industry has repeatedly been affected by issues such as workers' rights and child labor laws. Union workers in clothing manufacturing plants may strike against their employers, especially if their wages or medical benefits are less encouraging than workers in equivalent industries. Workers picketing their clothing employers impacts production. This can cause setbacks for retailers in getting spring or fall fashions on time. Activists who are not employed by the companies may also picket retailers who purchase clothing from countries known for breaching child labor laws. This negative publicity may impact a small clothing retailers' sales and profits. Also, a trade restriction against another company's imports would oblige clothing wholesalers to find different suppliers.

Technological Factors: Technological micro environmental factors affecting the clothing industry include availability of resources, demand and production. For example, the insufficiency of certain materials, such as leather, may compel retail and wholesale clothing companies to sell more artificial or substitute leather products. Retailers may raise the prices of cotton clothing if they encounter shortages of this raw material, as they must pay their manufacturers more. The introduction of new clothing styles by a rival can shift demand away from older fashions. Hence, a small clothing manufacturer may need to withdraw certain clothing lines and produce new ones that meet the needs of clients. Furthermore, clothing companies may add more complex equipment in their plants like robots, which may force companies to discharge some workers.

Organizational Constraints: Factors consist of population changes, norms, lifestyle, demographics and cultures are all a part of organizational constraints. These factors affect the clothing industry in diverse ways. For example, a small clothing manufacturer needs to produce styles that appeal to those of various cultures; especially if those cultural groups represent a big enough segment of its market. Contrarily, clothing manufacturers, wholesalers and retailers avoid creating too many clothing items that fall outside the norms of society, such as styles worn 50 years ago. Economic factors can have both positive and negative impacts on the clothing industry and is regarded as a significant organisational constraint. During economic boom periods, people have more disposable income. Hence, they can buy more clothing, increasing sales for clothing manufacturers, wholesalers and retailers. However, recessions have a contradictory effect. Sales for these ranges of clothing entities may be considerably lesser.

Task-3

Opening a new garment shop-

Introduction

This is a step-by-step system investigation plan on the clothing retail store which I would start. The goal is to keep this specific arrangement in order to help understand and assess the criteria necessary for it to develop into a successful business strategy.

Description of the business

It is a clothing retail store (a garment shop)

Market consideration

Clothing items targeted especially for teenagers and young adults. This would be the starting point since it is a bit challenging , especially keeping up with each of the seasonal trends.

Management Team

Since it is a small-business, hiring staff increases costs significantly, both in taxes and salary. To hire someone, looking for part - time help beforehand of the opening day would be suitable. I would attempt to provide them with sufficient training on how to run the cash register, information on the merchandise and store policies and regulations.

Technical Specifications and Production plan

I recommend purchasing retail fittings for the store. These may include display cases, counters, cash registers, clothing racks, telephones, credit card terminals, carpet, special lighting to highlight products, shopping bags dressing rooms, and gift wrap.

Marketing Plans

By adopting proper marketing strategies, I’d create a buzz in the market about my clothing retail store business. Marketing would be done in such a manner that it grabs the attention of my targeted customers. For example , the design of the store and the store’s website are made with the target customers in full consideration. Advertising would be done later since it needs to be well made in order to be successful and successful advertising can be costly.

Financial and Economic plans

A good spot is a great addition to the success of any retail business. Realtors would give estimates on traffic patterns near the store location. Convenience factors, such as handicap access and parking are important for the success of the garment shop. If the store was previously a clothing store, careful inquiries about the previous tenants are necessary.

Evaluation and conclusion

This system investigation provides a good outline and vision over the starting of the clothing retail store , committing to this plan would give a smooth start over the starting of a small business as such. However later on , modifications are necessary to keep up with new challenges introduced by this ever changing market.