Ex Naval Ships For Sale

Requirements Analysis (Part 1)

theoretical advantage that I'm studying and I am a refusal to hold things like a parrot, I wanted to write a little about requirements analysis for the subject of Software Engineering. I think it's the only way to learn concepts as theoretical.

The post will have two parts: the first is the one shown below, inserting few basic concepts and explaining what is the analysis of the system and things should be taken into account, the second one will go up later, or tomorrow, and will include techniques for determination of requirements, further analysis and how to be specified.

For starters, let's define a few concepts ...

A computer system is a set of elements arranged to perform a method, procedure or control by information processing. Within a computer system not only find software or hardware , but also different roles people , databases, documents or procedures.

A requirement, itself, is the condition or capacity needed by the user to reach solve a problem (or meet objectives.) In other words, you have to make the system reach.

The solution to a problem can be solved in 4 ways: manually, by software, by hardware or by combining the three.
This simple solution can be (via a simple software) or composite (through a more complex to automate all the actions.) In the case of the composite system is necessary to design the overall system before designing the software that integrates . The

systems engineering is the activity that is responsible for solving these problems. It is therefore necessary that the client integration asks us to participate in the development (in general) of the product by providing targets and constraints that must have the system. The engineer 's who developed the solution initially will be he who analyze system delimiting the area of \u200b\u200boperation, performance and functions. With this information you will need to define a set of solutions among which will choose the best considering, among other things, the existence of a product on the market that meets your needs (" is the case for the need for a road calculation, not develop it because there "), the cost might expect, the type of technology or to meet real needs.

TEST SYSTEM STAGE

1. Identify customer needs. We set the objectives to be achieved. If it is a product that is expected much impact among users, it should make a study of market.
2. study the feasibility of the system. This includes economic (analyzing impact of cost-benefit), technique (see if you can do or not), legal (or illegal determine violations that may cause the system) and alternative (to study the different solutions presented). Make
3. economic and technical analysis deeper.
4. determine the necessary functions and assign them to elements of the system.
5. Create a document that specifies the system definition. This document will serve as the basis for all subsequent system development.

Whether the solution is simple, as if made (system complex) have to make a analysis software requirements. Once we understand the problem by studying the system we have to reflect this understanding is a document. This is what is called requirements specification. The requirements that we considered could be:

• Functional: describes the inputs and outputs of the system, and the operations that take place between them. No functional
• : define the general qualities that must have the system. In other words, we can define these requirements and the limits of the possible solutions. These can be performance of design (standards compliance, hardware requirements, error handling, security) of external interfaces (everything related to the interaction of people, hardware or other software), quality of ( it is easy to use, maintain, that is expandable ...) or design decisions (module implementations).