Month: January 2013

Prototyping Model Often, a customer defines a set of general objectives for software but does not identify detailed input, processing, or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the adaptability of an operating system, or the form that human/machine interaction should take. In these, and many … Read more

Linear Sequential Model/Waterfall Model/Classic Life Cycle The linear sequential model, sometimes called the classic life cycle or the waterfall model, suggests a systematic, sequential approach to software development that begins at the system level and progresses through communication, planning, modeling, construction and deployment. The following given figure illustrates the linear sequential model for software engineering. … Read more

Problem Solving Loop : All software development can be characterized as a problem solving loop in which four distinct stages are encountered: status quo, problem definition, technical development, and solution integration.             Status quo represents the current state of affairs, problem definition identifies the specific problem to be solved, technical development … Read more

Software Process Model :  To solve actual problems in an industry setting, a software engineer or a team of engineers must incorporate a development strategy that encompasses the process, methods, and tools layers and the generic phases.  This strategy is often referred to as a process model. A process model for software engineering is chosen … Read more

CMMI (The Capability Maturity Model Integration):  The Software Engineering Institute (SEI) has developed a comprehensive model predicated on a set of software engineering capabilities that should be present as organizations reach different  levels of process maturity. To determine an organization’s current state of process maturity the CMMI uses two ways, (i) as a continuous model … Read more

Software Process:  Process defines a framework for a set of Key Process Areas (KPAs) that must be established for effective delivery of software engineering technology. This establishes the context in which technical methods are applied, work products such as models, documents, data, reports, forms, etc. are produced, milestones are established, quality is ensured, and change … Read more

The work associated with software engineering can be categorized into three generic phases, regardless of application area, project size, or complexity. Following flowchart encompasses the phases. Three Phases of the Generic View of Software Engineering: 01. Definition Phase:  The definition phase focuses on “what”. That is, during definition, the software engineer attempts to identify what … Read more

Key Process Areas (KPAs): The KPAs describe those software engineering functions that must be present to satisfy good practice at a particular level. Each KPA is described by identifying the following characteristics: 01. Goals: Goal is the target of a project or the overall objectives that the KPA must achieved. 02. Commitments: Requirements that must be met … Read more