System Analysis
|
|
Systems analysis is the interdisciplinary part of science, dealing with analysis of sets of interacting or entities, the systems, often prior to their automation as computer systems, and the interactions within those systems. This field is closely related to operations research. It is also "an explicit formal inquiry carried out to help someone, referred to as the decision maker, identify a better course of action and make a better decision than he might otherwise have made." |
Hainesbpo offers the following analyses:
- Accident analysis
- Business analysis
- Morphological analysis
- Software prototyping
- Spiral model
- Waterfall model
- Service-Oriented Modeling Framework
Accident Analysis
Accident Analysis is carried out in order to determine the cause or causes of an accident or series of accidents so as prevent further incidents of a similar kind. It is also known as accident investigation. It may be performed by a range of experts, including forensic scientists, forensic engineers or health and safety advisers.
Accident Analysis is performed in four steps:
Fact gathering after an accident has happened; a forensic process starts to gather all possible relevant facts that may contribute to understanding the accident.
Fact Analysis after the forensic process has been completed or at least delivered some results the facts are put together to give a "big picture." The history of the accident is reconstructed and checked for consistency and plausibility.
Conclusion Drawing if the accident history is sufficiently informative conclusions can be drawn about causation and contributing factors.
Countermeasures in some cases the development of countermeasures is desired or recommendations have to be issued to prevent further accidents of the same kind.
Our Methods:-
There exist numerous forms of Accident Analysis methods. These can be divided into three categories (in alphabetical order):
Causal Analysis uses the principle of causality to determine the course of events. Though people casually speak of a "chain of events" results from Causal Analysis usually have the form of directed a-cyclic graphs. The nodes being events and the edges the cause-effect relations.
Methods of Causal Analysis differ in their respective notion of causation. Expert Analysis relies on the knowledge and experience of field experts. This form of analysis usually lacks a rigorous (formal/semiformal) methodological approach. This usually affects falsify-ability and objectivity of analyses. This is of importance when conclusions are heavily disputed among experts.
Organisational Analysis relies on systemic theories of organisation. Most theories imply that if systems behaviors’ stayed within the bounds of the ideal organisation then no accidents can occur. Organisational Analysis can be falsified and results from analyses can be checked for objectivity. Choosing an organisational theory for accident analysis comes implies the assumption that the system to be analysed conforms to that theory.
Business Analysis
Business analysis helps an organization to improve how it conducts its functions and activities in order to reduce overall costs, provide more efficient use of resources, and better support customers. It introduces the notion of process orientation, of concentrating on and rethinking end-to-end activities that create value for customers, while removing unnecessary, non-value added work. The person who carries out this task is called a business analyst or BA.
Those BAs who work solely on developing software systems may be called IT Business Analysts or Technical Business Analysts.
Hainesbpo as such reduces waste and complete projects on time and provides appropriate documents and improve project efficiency.
Roles of Business Analysts at Hainesbpo:-
As the scope of business analysis is very wide, there has been a tendency for business analysts to specialize in one of the three sets of activities which constitute the scope of business analysis.1. Strategist
Organisations need to focus on strategic matters on a more or less continuous basis in the modern business world. Business analysts, serving this need, are well-versed in analyzing the strategic profile of the organization and its environment, advising senior management on suitable policies, and the effects of policy decisions.
2. Architect
Organizations may need to introduce change to solve business problems which may have been identified by the strategic analysis, referred to above. Business analysts contribute by analyzing objectives, processes and resources, and suggesting ways by which re-design (BPR), or improvements (BPI) could be made. Particular skills of this type of analyst are "soft skills", such as knowledge of the business, requirements engineering, stakeholder analysis, and some "hard skills", such as business process modeling. Although the role requires an awareness of technology and its uses, it is not an IT-focused role.
Three elements are essential to this aspect of the business analysis effort: the redesign of core business processes; the application of enabling technologies to support the new core processes; and the management of organizational change. This aspect of business analysis is also called "business process improvement" (BPI), or "reengineering".
Software prototyping
Software prototyping, a possible activity during software development, is the creation of prototypes, i.e., incomplete versions of the software program being developed.
A prototype typically implements only a small subset of the features of the eventual program, and the implementation may be completely different from that of the eventual product.
The purpose of a prototype is to allow users of the software to evaluate proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions.
Prototyping has several benefits:
The software designer and implementer can obtain feedback from the users early in the project. The client and the contractor can compare if the software made matches the software specification, according to which the software program is built. It also allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met.
The spiral model
The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. Also known as the spiral lifecycle model, it is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive and complicated projects.
The Spiral Model
The steps in the spiral model can be generalized as follows:
The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
- A preliminary design is created for the new system.
- A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
- A second prototype is evolved by a fourfold procedure:
- evaluating the first prototype in terms of its strengths, weaknesses, and risks;
- defining the requirements of the second prototype;
- planning and designing the second prototype;
- Constructing and testing the second prototype.
At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer's judgment, result in a less-than-satisfactory final product.
The existing prototype is evaluated in the same manner as was the previous prototype, and, if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
The final system is constructed, based on the refined prototype.
The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a continuing basis to prevent large-scale failures and to minimize downtime.
The spiral model is used most often in large projects. For smaller projects, the concept of agile software development is becoming a viable alternative. The US military has adopted the spiral model for its Future Combat Systems program.
Advantages
Estimates (i.e. budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier.
It is more able to cope with the changes that software development generally entails.
Software engineers can get their hands in and start working on the core of a project earlier.