Requirement analysis and prototyping for twinning projects
Team Builders: 3006 Liang Yi & 3010 Ai Xiaohan
In "The Method of Construction (Zou Xin Edition)", the NABCD model is introduced in the framework section of competitive demand analysis
N needs (need), to solve the needs of users;
A, approach, the means to solve the needs;
B, benefit, what benefits the product will bring to customers/users;
C, competition (competitors), market competition, see the pros and cons of the situation;
D, promotion (delivery), how to put the product in the hands of users
designing process
According to the requirements of this assignment, the two of us are from different classroom groups. At the beginning, we didn't have any good ideas, and we couldn't think of any innovations. After reading different versions of mobile phone memos of different brands, we also asked some students around me about their habits of using memos. We began to have some ideas and discussed In the process, although the ideas were different, but in the end the same way, the homework was finally completed.
Similarly, here I briefly analyze the design process of the two of us using the NABCD model:
N: In our daily life, memos are a good thing for us to manage time and help us record important things, but we do not use memos very often, and we often forget some to-do matters. This actually reflects that so far, the memo function that comes with the mobile phone is not perfect or intelligent enough, so we have not been able to use it well. This gives us a good idea - if there is a smart memo, we don't need to type it out one by one every time, even if there is one person in the team who can remind the whole team, efficiency is not higher? So we need a smarter reminder to manage our time and remind us when and where to do things.
A: After understanding the customer's needs, my teammates and I began to analyze and discuss how to solve the problem and meet the needs:
1. First of all, between the web and the app, we choose the latter; because we receive reminders on the mobile side more often, we rarely log in to the web page to view. Even if the network is disconnected, the webpage cannot push reminders in time.
2. Then we refer to some existing memos on our own mobile phones (for interface design) and some existing memorandum apps in the application market (for functions and user feedback), and we briefly simulate some interfaces and functions. For example, log in, manually add memos, the system actively identifies the time, place, events and other main information of the information and automatically sets reminders and other processes.
3. Improve and design our highlight functions, clarify the advantages and disadvantages of each function, and improve our project
4. Modify the model and improve it continuously.
Our approach here has the following highlights:
- Design Highlight 1 : Information filtering and automatic reminder function. In response to the sudden arrival of an event or an emergency situation, we may be busy with other things and have no time to manually enter the reminder. At this time, just copy and paste the event notification into the memo app, and it will automatically identify the time, location and key events such as key words , and automatically set reminders.
- Design Highlight 2 : Interactive function. In the traditional impression, the memo is a matter for oneself, but some events (such as class meetings, meetings in the same department, exams) are carried out with classmates around them. If someone uses this app with you and adds them as friends, a When a person sets a reminder, they can choose the friend they want to remind, and the reminder will also be automatically added to the friend's memo that was "named".
- Design Highlight 3 : The interface is simple and friendly Many app interfaces are bright and colorful, which will not arouse much interest from users, and even make people visually tired. The simple and friendly interface can make users have a better experience
B: Changed the original manual "code word memo" mode, which not only realizes the intelligent information reminder, but also through our design, the original single "single-handed task completion" can be changed to remind each other with "teammates" and supervise each other . When you see your things to be done being done one by one, you will also get a sense of accomplishment. The communication function is added, and it can also reduce the wrong input of some important information when we set the memo.
C: If there is competitive pressure in this prototype design, firstly, it comes from different pairs of students, and secondly, it comes from existing memo software and other small programs with similar functions.
D: If accepted by the teacher, the project will be the next assignment for our pairing project. If the teacher does not accept it, our pairing will not be able to continue coding this time next week. If it can be completed, compared to the less intelligent traditional memorandum, as long as we successfully recommend it to our classmates, it will soon be welcomed.
Our project is currently in the prototype stage and cannot provide specific information such as development and recording time, but what we can do is estimate the project time.
PSP
| PSP2.1 |
Personal Software Process Stages |
Estimated time (minutes) |
actual time (minute) |
|
| Planning |
plan |
10 |
30 |
|
| · Estimate |
· Estimate how much time the task will take |
10 |
15 |
|
| Development |
develop |
655 |
500 |
|
| · Analysis |
· Requirements analysis (including learning new technologies) |
30 |
10 |
|
| · Design Spec |
· Generate design documentation |
30 |
15 |
|
| · Design Review |
· Design review (review design documents with colleagues) |
10 |
10 |
|
| · Coding Standard |
Code Specifications (to develop appropriate specifications for current development) |
5 |
|
|
| · Design |
· Specific design |
40 |
|
|
| · Coding |
· Specific code |
5h*60 |
|
|
| · Code Review |
· Code review |
1h*60 |
|
|
| · Test |
· Testing (self-testing, modifying code, committing changes) |
3h*60 |
|
|
| Reporting |
Report |
290 |
|
|
| · Test Report |
· Test report + blog |
4h*60 |
|
|
| · Size Measurement |
· Computational workload |
10 |
|
|
| · Postmortem & Process Improvement Plan |
· Summarize after the fact and propose a process improvement plan |
40 |
|
|
| total |
955 |
|
|
experience
This time, I paired up with students from different groups, and I feel that I have gained a lot. Only two people work together, and the workload will increase accordingly. From determining the project, to the design and refinement of functions, and considering applicability and competitors, it is more difficult than completing a "XX system" by yourself. Thank you very much for the trust and patience of "Friends", and the cooperation is pleasant.
Liang Yi
