08-08-2012, 03:48 PM
Result management system
Result management system.doc (Size: 2.74 MB / Downloads: 108)
Project monitering system
The waterfall model:-
Sequence of models executed top to bottom
Each activity is validated/tested before proceeding to next step
Activities:-
System feasibility, system design, system analysis, programme design, coding, testing, installation, operation and support, maintenance, retirement
Strength of waterfall model
Utilization of staff
Good project control
Easy to use
Easy to understand
Provides structure to inexperienced staff
Milestones are well understood
Sets requirement stability
Good for management control
Works well when quality is more important than cost and schedule
Feasibility study
A feasibility study is defined as an evaluation or analysis of the potential impact of a
proposed project or program. A feasibility study is conducted to assist decision-makers
in determining whether or not to implement a particular project or program. The
feasibility study is based on extensive research on both the current practices and the
proposed project/program and its impact on the school foodservice operation. The
feasibility study will contain extensive data related to financial and operational impact
and will include advantages and disadvantages of both the current situation and the
proposed plan.
The feasibility study is conducted to assist the decision-makers in making the decision
that will be in the best interest of the school foodservice operation. The extensive
research, conducted in a non-biased manner, will provide data upon which to base a
decision.
Top-down design principle
The essential idea of top-down design is that the specification is viewed as describing a black box for the program? The designer should decide how the internals of the black box is constructed from smaller black boxe: and that those inner black boxes be specified. This process is then repeated for those inner boxes, and so on till the black boxes can be coded directly.
A top down design approach starts by identifying the major modules of the system, decomposing them into their lower level modules and iterating until the desired level of detail is achieved. This is stepwise refinement; starting from an abstract design, in each step the design is refined to a more concrete level, until we reach a level where no more refinement is needed and the design can be implemented directly. Most design mathadology is based on this approach and this is suitable, if the specifications are clear and development is from the scratch. If coding of a part starts soon after its design, nothing can be tested until all the subordinate modules are coded.
System design
Systems design is the process of defining the architecture, components, modules, interfaces, and data for a system to satisfy specifiedrequirements. One could see it as the application of systems theory to product development. There is some overlap with the disciplines ofsystems analysis, systems architecture and systems engineering.[1][2] If the broader topic of product development "blends the perspective of marketing, design, and manufacturing into a single approach to product development,"[3] then design is the act of taking the marketing information and creating the design of the product to be manufactured. Systems design is therefore the process of defining and developingsystems to satisfy specified requirements of the user. Until the 1990s systems design had a crucial and respected role in the data processing industry. In the 1990s standardization of hardware and software resulted in the ability to build modular systems. The increasing importance of software running on generic platforms has enhanced the discipline of software engineering.
Testing methodology
There are different types of software testing methodologies used in the field of software testing and quality assurance. In the following article, we'll take a look at various software testing techniques and methodologies that are in practice today
Software testing is an integral part of the software development life cycle (SDLC). Testing a piece of code effectively and efficiently is equally important, if not more, to writing it. So what is software testing? Well, for those who are new to software testing and quality assurance, here are few useful facts.
Software testing is nothing but subjecting a piece of code to both, controlled and uncontrolled operating conditions, in an attempt to observe the output and examining whether it is in accordance with certain pre-specified conditions. Different sets of test cases and testing strategies are prepared, all of which are aimed at achieving one common goal - removing bugs and errors from the code and making the software error-free and capable of providing accurate and optimum outputs. There are different types of software testing techniques and methodologies