Transcript Slide 1
แนวทางการบริหารจัดการโครงการที่ดี (Scope = Resources + Time) ออกแบบ แกนตัง้ การสร้ างความพร้ อม จัดสรร ทรั พยารที่จากัดของโครงการ CSF of ICT Infrastructure (CBIS/ TBIS) คือ>> •Goals Architecture People ware •Business Process Architecture Hardware/ Software Of Computer and Network •Data INFORMATION Architecture •Application Architecture BUSINESS RULE / ACTS:Structured Rules / Code of Conducts/ ETHICS •ICT Infrastructure Architecture BUDGETS •ICT Good Governance Architecture บรรลุแผนICT ขับเคลื่อนห่ วงโซ่ คุณค่ า 4 ส่ งเสริม สนับสนุน และ การคิด ~40% -50% ขั ้นตอน 1 การศึกษา วิเคราะห์ และออก แบบเป้า ประสงค์ กระบวนงาน และข้ อมูล การทา ขอบเขต การ บริหารโครงการ ไอทีท่ ีดี ~30% 40% ขัน้ ตอน 2 การจัดทา และพัฒนา ซอฟต์ แวร์ การแก้ ไข ปิ ดโครงการ ~-30% -10% ขัน้ ตอน 3 การทดสอบและปรั ประบบ ฝึ กอบรม ใช้ งาน และจัดการศูนย์ ข้อมูล. เพื่อ MA กาหนดกรอบ เวลา….> กระบวนงานI CTขับ เคลื่อนห่ วงโซ่ Software Back Bone ขับเคลื่อน Digital Firms ขับ เคลื่อนห่ วงโซ่ SW Project Management developed by SOFTWARE ENGINEERING CONTEXT: SE 1. FIELDS:- Requirements analysis • Systems analysis • Software design • Computer programming • Formal methods • Software testing • Software deployment • Software maintenance 2. CONCEPT:- Data modeling • Enterprise architecture • Functional specification • Modeling language • Programming paradigm • Software • Software architecture • Software development methodology • Software development process • Software quality • Software quality assurance • Structured analysis 3. ORIENTATIONS:- Agile • Aspect-oriented • Object orientation • Ontology • Service orientation • SDLC 5. MODELS:- Development models (Agile • Iterative model • RUP • Scrum • Spiral model • Waterfall model • XP • V-Model) Other models (Automotive SPICE • CMMI • Data model • Function model • Information model • Metamodeling • Object model • Systems model • View model) Modeling Language (IDEF • UML) 5. SOFTWARE ENGINEERS:- 6. RELATED FIELDS:- Computer science • Computer engineering • Enterprise engineering • History • Management • Mathematics • Project management • Quality management • Software ergonomics • Systems engineering Kent Beck • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham • Ole-Johan Dahl • Tom DeMarco • Martin Fowler • C. A. R. Hoare • Watts Humphrey • Michael A. Jackson • Ivar Jacobson • Craig Larman • James Martin • Bertrand Meyer • David Parnas • Winston W. Royce • James Rumbaugh • Niklaus Wirth • Edward Yourdon SOFTWARE ENGINEERING: SE 1. Fields •Requirements analysis • Systems analysis • Software design • Computer programming • Formal methods • Software testing • Software deployment • Software maintenance SOFTWARE ENGINEERING: SE 2 2. Concepts •Data modeling • Enterprise architecture • Functional specification •Modeling language • Programming paradigm • Software • Software architecture • Software development methodology • Software development process • Software quality • Software quality assurance • Structured analysis SOFTWARE ENGINEERING: SE 3 3. Orientations •Agile • Aspect-oriented • Object orientation • Ontology •Service orientation • SDLC SOFTWARE ENGINEERING: SE 4 4. Models 1) Development models • Agile • Iterative model • RUP • Scrum • Spiral model • Waterfall model • XP • V-Model SOFTWARE ENGINEERING: SE 5 2) Other models • Automotive SPICE • CMMI • Data model • Function model • Information model • Metamodeling • Object model • Systems model • View model SOFTWARE ENGINEERING: SE 6 3) Modeling languages • IDEF • UML SOFTWARE ENGINEERING: SE 7 5. Software Engineers •Kent Beck • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham • Ole-Johan Dahl • Tom DeMarco • Martin Fowler • C. A. R. Hoare • Watts Humphrey • Michael A. Jackson • Ivar Jacobson • Craig Larman • James Martin • Bertrand Meyer • David Parnas • Winston W. Royce • James Rumbaugh • Niklaus Wirth • Edward Yourdon SOFTWARE ENGINEERING: SE 8 6. Related fields 1) Computer science 2) Computer engineering 3) Enterprise engineering 4) History 5) Management 6) Mathematics 7) Project management 8) Quality management 9) Software ergonomics 10) Systems engineering Requirements analysis Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users.ฃ Requirements analysis is critical to the success of a development project.[2] Requirements must be documented, actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Requirements can be functional and non-functional. Requirements analysis is the first stage in the systems engineering process and software development process Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users. Requirements analysis is critical to the success of a development project.[2] Requirements must be documented, actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Requirements can be functional and non-functional.