06 Jul For the ESPN website, it is time to take a deeper dive into the

For the ESPN website, it is time to take a deeper dive into the requirements of your website, and how the system flows and operates…and will have THREE deliverables for this project…they are as follows: · Project Definition Document· System Model Document· Component Model DocumentLet’s take a look at each one of these in more detail…Project Definition DocumentA Project Definition Document acts as a contract between the business and the IT organization that is building the system…it speaks to the requirements of the system and the expectations of all the stakeholders…it is the one document that is the reference point for all future development…Keep in mind that in “real life” this document CAN and is often updated…but only after the proposed changes are reviewed and approved by all the stakeholders…for the purposed of this project, there will be NO changes to the original document…All of the deliverables are based on topics reviewed in the weekly Power Points…you can also find these topics in SWEBOK…use both of these as references for the information that you need to provide…What you should NOT do is look for these exact items on the internet and do a copy/paste…I expect the documents to be IN THE FORMAT THAT WAS REVIEWED IN CLASS…if you give me information in any other format, you will receive a ZERO…I have listed below EXACTLY what I am looking for…you must follow this outline…if there are items not in this outline that you would like to include you must get approval from me FIRST…if you do not get my approval and you include things that I did not ask for, you will lose points…You must provide the following:· Project Definition…o What are we building?…o Project scope…· Project Deliverables…o What are the deliverables?…o Needs to be specific enough so that everyone has the same expectations of what is being developed…· Identification of Stakeholders…o Who is the client?…o Who are we?…o Who is the project sponsor?…o Who are the end users?…o Who are the external stakeholders?…· Functional requirements…o Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations…o May state what the system should not do…· Non-functional requirements…o Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc….o Often applies to the system as a whole rather than individual features or services…· Domain requirements…o Constraints on the system from the domain of operation…· Non-Functional Classifications…o Product requirements: Requirements which specify that the delivered product must behave in a particular way…e.g. execution speed, reliability, etc….o Organizational requirements: Requirements which are a consequence of organizational policies and procedures…e.g. process standards used, implementation requirements, etc…o External requirements: Requirements which arise from factors which are external to the system and its development process…e.g. interoperability requirements, legislative requirements, etc…· Ethnography…