2014 Access to HE Computing Alex Hyslop [SANDWICH ON THE GO!] -   Table of

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

In order to meet the criteria for a merit, you must also satisfy the following additional criteria: -

All projects are defined by the purpose, objectives and deliverables. Properly defining these, as well as the other aspects of the project management plan will

The next step in the process is system analysis. This second stage involves gathering requirements, such as documenting the strengths and weaknesses of the current system, having discussions with the users to understand their roles and needs. This is an integral part of the life cycle as employees are the most important asset a company has. Baya, Gruman, & Mathaisel state, “information technology

Project ____ may be defined as a test of whether a project has met scope, time, and cost goals.

1-Project: " An endeavor in which human, material, and financial resources are organized in a novel way, to undertake a unique scope of work, of given specification, within constraints of cost and time, so as to achieve beneficial change defined by quantitative and qualitative objectives"(Turner & Müller 2003).

Chapter one will introduce the project proposal by giving a small description of the project, stating the project problems and identifying the solutions to the problem. Chapter two will identify the background behind the project problem by identifying the problem history, the relevance of the problem, the occurrence and reasons behind the particular problem, whether the problem has been solved and what has been achieved, whether the problems has solutions that solve it or similar systems that do not have the said problem and finally, the possible improvements that can be done to solve the problem. Chapter three will summarize what the intended project proposal achievement. Chapter four will look at the elements and scope of the project by breaking it down into the procedure required to actualize the project and the required tools of engagement. This chapter will also discuss the challenges and issues to be faced during implementation of the project such as the type of skills and equipment needed. The deliverables will also be discussed such as the project report, prototype, program and model describing the products of the project in detail. This chapter will emphasize the intended contributions of the project, timeline and budget. Finally, the last chapter that is chapter five will discuss the conclusion summary of the entire project

(Project definition: Planned set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations)

For the successful completion of the project, the management needs to outline the requirements in terms of both input and output incorporating necessary steps such as research, personnel, technical knowledge as well as the financial implications. According to Nokes (2007), project

1) Before using any DBMS, the creators should have created a data model from the users' requirements.

A project is a unique venture with specific start and end dates. This is different from an ongoing task that doesn't have an end date. Projects often involve different parts of an organization. Constraints on project include cost, schedule, resources, and quality. There is a give and take between these items i.e. you can't have it all. Usually projects are divisible into stages or phases each with their own set of priorities and goals.

A project is defined as a unique set of co-ordinated activities with a finite duration, defined cost and performance parameters and clear outputs to support specific business objectives.

BIS aims for identification and prioritization of components of system by correlating system’s business processes to these components. The information extracted will be then used for evaluating the impact that the system unavailability will have on processes.

Project Objectives: The way in which the projects are defined and implemented. The sufficient comprehension of a project is based on

John W. Brackett states that “The subject of software requirements is often given far less attention in software engineering education Because of the dependence of this module on than software design, even though its importance is Software Specification: The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the inter-faces to people, to machines and to other software systems. No part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later” (Brackett, 1996). This paper will give the definition of software requirements; how they are determined, specified, documented, and who is included in the process of requirements; and the roles these individuals play in processing requirements. The end of this paper will bring all of these concepts together to help explain why these processes are extremely important.