An OA project, the original demand document has been unrecognizable, thanks to version management, the last version before the demand difference analysis: --------------------- -------------------------------------------------- ---------------- 3.1.2.6. Arrange another user schedule Users Click "Add Schedule" button in the View Colleague Schedule page System Display Schedule Add Page User Selection Time, fill in the transaction details, expect time, choose the transaction type, whether the user can click "Submit" button System Check Time Conflict Time No Conflict System Record New Transaction System Display Operation Success Page There is a time conflict system Prompt a conflict-related transaction, prompting whether to modify transactions User confirmation add system Record new transaction System display operation Success page Users Select Modify Transaction System Return to Schedule Add Page ---------------- -------------------------------------------------- -------------------------
After writing this version, I will go to do demand difference analysis. Other colleagues start to make coding according to the tentative demand document (time is urgent, the design is skipped, and the later design document is from
Code reverse engineering process.
During my business trip, I have a colleague, and a schedule should be assigned to multiple colleagues in some cases, so a "Schedule" concept, that is, a schedule
Take grass first and then assign multiple users. The brothers who are responsible for developing this module feel that it makes sense, so I developed this.
After the business trip came back, I updated the demand document, but this part of the user did not make an objection, so there was no modification. It was basically completed until last week, starting SIT this Monday. At this time, I found out that I have to arrange a schedule now, I must first draft a "Scrand Draft" and assign it to yourself or others. This is better than I want to send an email, I must write an email to save it into the draft box, and then go to the draft box to find it.
This is certainly unacceptable, so the brothers ask the brothers to modify as little as possible, that is to say to remove the draft of the draft, this process is packaged, and automatically saved
End it to send it. However, due to the process of checking the time conflict and the response is not designed for draft, the process, design and re-coding. Tonight with the brothers to correct this problem, I hope to start SIT tomorrow.
"A schedule should be assigned to multiple colleagues in some cases," is a demand gold plated without being confirmed, and it is probably designed to design when it is not carefully examined, causing today's dilemma.
