Management Information System Requirements research and Analysis guide

Summary:

This article is in the management information system needs the research practice and the study some experience summary, some is own experience, some comes from the expert's book or the article, hoped to share with everybody, and has played the role which, if has the improper place welcome to correct.

I. Definition of software requirements

The requirements defined in the IEEE Software Engineering Standard Glossary (1997) are:

(1) The user to solve the problem or to achieve the objectives of the necessary conditions or capabilities;

(2) System or system components to meet the contract, standards, norms or other formal requirements of the document required to have the conditions or capabilities;

(3) A document description that reflects the above conditions and capabilities.

Ii. Several aspects of demand analysis

The requirement analysis can be divided into four stages, such as problem identification, analysis and synthesis, compiling requirement analysis documents and requirement evaluation, including the following aspects: identifying the user classes that the software expects, acquiring the needs of each user, understanding the actual user tasks and objectives, and the business requirements that these tasks support The information of the analyst and the user to distinguish the user's task requirements, functional requirements, business rules, quality attributes, proposed solutions, and additional information; Divide the system-level requirements into subsystems and allocate a portion of the requirements to software components; Discuss the importance of the relevant quality attributes; To prepare the user requirements for the requirements specification and model, to review the requirements specification and to ensure a consensus with the user.

The components of the software requirements are shown in the following illustration:

Specification of requirements Documentation

A, three methods of writing

1, the use of good structured and natural language to write text-type documents;

2, the establishment of a graphical model, these models can describe the transformation process, System State, and their changes, data relations, logical flow or object classes and their relationship;

3, the preparation of formal specifications, which can be used mathematically accurate formal logic language to define requirements.

Multiple authoring methods can be used in the same document, depending on the need to choose, or complement each other, to be able to understand the needs of the purpose.

B. The results should be

1, the Business manual processing of the flow of text description;

2, each Business manual processing flow chart;

3, each Business manual processing of the input and output forms, data sources;

4, the Target Software system function division (schematic and text description);

5, the target software system in the business process text description;

6, the target software system in the business Process flow chart (model);

7, in the target software system each business handles each link data, the data collection way, the internal relation analysis of the datum.

8, the target software system user interface diagram, all kinds of system Logic model diagram and description

C, document Tools recommended

1, the survey results "Requirements analysis Manual" format reference to the development of document templates;

2, Unit organization chart, function module decomposition diagram in Visio drawing, or directly with the drawing tools in Word;

3, Business flow chart with the flowchart template in Visio to draw;

4. The system logic model uses rose to draw the UML template in Visio;

5. The software user interface is drawn with the WIN95 user interface template in Visio;

6, the data physics model uses the Powerdesiner to draw;

D, requirements document writing principles

1, the sentence is short and complete, with correct grammar, spelling and punctuation;

2. The terms used are consistent with those defined in the glossary;

3. The requirement statement should have a consistent style, such as "system must ..." Or "User must ..." and follow a behavioral action and observable results. ；

4, avoid the use of vague, subjective terminology, reduce uncertainty, such as "user-friendly interface, easy to operate";

5, avoid the use of comparative words, such as "improve", should quantify the extent of improvement.