Preface
I have read two books and have never written any requirement analysis. Therefore, the writing must be superficial, so I only put it on the home page to give my experts some comments, I think a lot of people do not know how to write the requirement analysis. Let's talk about it here and learn from each other. There are only a few people on the homepage, this may be a bit selfish. If you feel that the homepage is out of the way and you are notified in time, I will immediately win it. haha
Project Background
1. last year, I read requirement analysis and system design UML and model applications, I have been searching for something to practice, and I almost forgot about it at the time, so I can review and practice it.
2.I used to use the family-appropriate wealth management software produced by a software company in China. From the first piracy to the later purchase of genuine software, the new version seems to be charged on a yearly basis and I think it is too expensive, if you want to develop a similar function and improve the inconvenience in use, create a free version.
Scenario 2 Statement
after a user logs on to the system , record consumption / Revenue statement , including records that may be missed a few days ago on the current day . Each flow account includes the consumed content, amount, date, and set of books. The content (purchased products, non-products are based on virtual products) adopts bar code management and custom bar code management for content without bar code. The amount involves the unit (RMB, USD ). A set of books involves the initialization of a set of books.
Scenario 3 Analysis
1.From the scenario statement, we can find out the system participants: Users
2.Scenario statements can be divided into requirements and corresponding use cases.
A)System Support user logon-system Logon
B) set creation and initialization-set management
C) product (consumption content) Addition, price change trend, maintenance, and other content. (Currently, the price of the products used by the financial management software is subject to the price entered last time, covering the previous price. In this way, the amount of purchased products cannot be calculated) -- product management
D)Amount conversion problem. (For example, when I enter a flow account after I return for a shopping in Hong Kong, there is a conversion between Hong Kong dollar and RMB, which is not supported by the wealth management software I use) -- exchange rate management
E) the input and modification of the flow account will involve the adjustment of the remaining amount-the flow account management.
Conclusion
After reading requirement analysis and system design, this seems to be the first step in software requirement analysis. I don't know if my understanding is correct, or what are the omissions in the first step of requirement analysis. the second step should be to write a specific description of the above case.
The development platform is optimistic about PRISM, and there is another persistent problem that I don't know how to consider.