1、ISDC SHA UI RequirementProcedure CircleDocument InformationProject Name:Department Manager:Peter Yong Document Version No: 1.0Document Version Date: 11/08/2019Prepared By: Joe Chen Preparation Date: 11/07/2008Version HistoryVer. No. Ver. Date Revised By Description Filename1.0 11/08/2019 JoeLast Mod
2、ified: 2019/8/11 OOCL ISDC/SHA Confidential and ProprietaryPage 2 of 5CONTENTISDC SHA UI REQUIREMENT PROCEDURE CIRCLE.1Objective 3Project Life-cycle and Milestones3Phases and Deliverables4Supplementary notice:5Last Modified: 2019/8/11 OOCL ISDC/SHA Confidential and ProprietaryPage 3 of 5ObjectiveTo
3、standardize UI requirement raise process for better project managementProject Life-cycle and MilestonesLast Modified: 2019/8/11 OOCL ISDC/SHA Confidential and ProprietaryPage 4 of 5Phases and DeliverablesPhases Events Stake holders Descriptions Deliverable documentsPhase 1 External UE investigation
4、from User groupsUI, User groups(CPI, CSV,OPS)The periodically investigation of User Experience from the various user groups lead by BA and UI. UI Requirement Proposal Personas(Optional) Scenario docs(Optional)Phase 1Internal UE investigation from Expertise groupsPMs, BAs, QAs, UI, developersUI repre
5、sentative BA and all UI concerned colleagues raise the issue to UI E-mails UI Requirement Proposal Scenario doc(Optional)Phase 2UI related or Weekly BA meeting, discuss the requirementUI, All Project BAs UI collects UI requirement weekly and shares among BA team or UI related BAs per weekly meeting
6、with the purpose to have acknowledgement and alignment in BA team 1st Prepared prototype Scenario doc UI Req. Proposal E-mail of UI alignmentPhase 3Presentation to Tech leadersTech Specialists, UI related BAs, UIUI recap to summarize the present situation and the purpose / objective of the standardi
7、zation to UI Tech Specialists, so as to seek acknowledgement from all project Tech specialists, and they can have meetings if any disputes Scenario doc UI Req. Summary Review meeting recapPhase 4Follow up with BA, Tech specialistsBAs, Tech Specialists, UI UI will follow up with BA representatives an
8、d front-stage tech specialists to refine the requirement and standard UI Req. SummaryPhase 5PM monthly UI meeting PMs, Tech Specialists, BA representative, UIReviewed before Monthly UI meeting led by PMs, and get endorsement from PMs in the meetingPublish the endorsed/finalized UI Guideline updates.
9、 Updated UI Guideline UI Update E-mailPhase 6Dev. team meeting/ ImplementationTech Specialists, BA representative, PM, developers, UIBA hold meetings to introduce the new Requirement to all related developers, front-stage representative developer shall assist. (The result may group-send email to dev
10、elopers as well.) Updated UI Guideline Meeting RecapPhase 7Feedback UI, BA, User groups UI collect the feedback from focused groups, such as CPI, CSV, and OPS. UI Survey reportLast Modified: 2019/8/11 OOCL ISDC/SHA Confidential and ProprietaryPage 5 of 5Supplementary notice:In case some urgent UI im
11、provements, after confirm in the UI related BA meeting, UI will quickly collect all PMs and tech specialists response and agreements so as to keep the consistency of UI guideline, and then publish the UI standard for implementation. If therere any disputes occur, it is still necessary to hand over to PM monthly UI meeting or hold the meeting for emergence. But this urgent schedule is not recommended unless the UI requirement need to accomplish before the PM meeting.
