Practice Iconix in X project (i) User requirements research and use case modeling

X project is a set of service company sales and customer service system. Our department is a system-open party. As a developer, I was in the middle of a project and was engaged in an enthusiastic demand survey.

Demand side is the company Y department (can be understood as marketing support technology Department), so the demand side is to understand the technology drop! This has brought great convenience to the demand research.

The following is a brief introduction to the entire requirements survey process, omitting some details.

Research process

0, the project manager and technical leader and the demand side for the first time communication. (I did not participate)

This process, I was not involved. The main thing to do is to have a preliminary understanding of the needs of the Y department.

1, the demand side proposed "X System characteristics Demand V1" version;

This was the result of the first communication, and the demand side sent this "feature requirement" to our project team (four people involved in demand research).

2, for the "x system characteristics Requirements V1" project team for the first time to communicate, and organized into "X system characteristics Demand v1-recommendations and questions";

Get this "feature requirements", the internal communication has been many times. Finally, a "proposal and doubt" was made.

3, "X system characteristics Demand v1-suggestions and questions" to the demand side, and the demand side for the second communication, and the "X system characteristics Requirements V2" version;

This is my first contact with the demand side, mainly in response to our questions, the demand side gave an explanation, and accepted some suggestions, and out of a version of "feature requirements."

4, for "x system characteristics Requirements V2", the project team to abstract the system-level functional modules;

For the new version of the "feature requirements", we first think of the abstract into the system function module, and determined the system functional modules of a large class.

5, the members of the project team use 1-2 days time to the first level of functional modules refinement, functional refinement to Level 3 (1,1.1,1.1.1), and organized into "X system function Requirements V1".

Several colleagues who participated in the demand survey respectively refined the first level module and sorted out a system function requirement.

6, the "X system function requirements V1" to the demand side, and the demand side for the third communication.

Before communicating, what we think about is whether the system function is perfect. At the meeting, the demand department suggested that such a functional requirement was not something they needed.

Because they also need to talk to more than 10 users of the system. What they want to see is the mapping between actor, UC, and actor and UC----that we need to design the use-case model of the system.