버전용 도움말 콘텐츠:

Once the project has been formally initialized the analysis phases can start:

  • Investing sufficient time and effort in the design of your project can prevent unwelcome surprises later. 
  • Complete your design before starting development as the design can affect the performance of your entire website. 
  • Often various studies, of ever-increasing detail, are performed to define, review and refine issues. 
  • A final review can result in a further Go or No-Go decision for implementation of the project.

The issues for analysis can include:

  • Use Cases

    • The customer should define their requirements as Use Cases. These define required functionality in terms of the interaction between Actors (roles which initiate certain actions) and the system.
    • These will then be used for further analysis, and for testing, in particular acceptance testing.
  • Functional Requirement Specifications

    • All functional requirements must be analyzed.
  • Detailed Requirement Specifications

    • A detailed analysis of all requirements should be made and clearly documented.
  • Design Proposal

    • The design of your project should be defined. Performance requirements will influence this.
  • Review of Target Metrics

    • The metrics must be referred to when developing the design. The design must either meet the target metrics, or justify any compatibilities in preparation for a review.
  • Review of Target Metrics

    • The metrics must be referred to when developing the design. The design must either meet the target metrics, or justify any compatibilities in preparation for a review.
  • Budget

    • A budget proposal must be drawn up covering all aspects from third-party software to development resources.
  • Planning Requirements

    • Not only must the budget be assigned all other aspects must be considered; in particular you must ensure that the specific resources you require are available as and when you need them.
  • Commitment

    • Ensure that your development team commit to the functional and performance requirements with regard to the timelines being imposed.
  • Project Plan

    • This should be drawn up and circulated to all people involved in the project. It must also be also be maintained and updated as changes occur.

이 작업에는 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License의 라이센스가 부여되었습니다.  Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.

법적 고지 사항   |   온라인 개인 정보 보호 정책