Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
The objectives of this chapter are to describe the components of a typical enterprise's value system and value chain and to discuss the procedures for developing models of enterprise value systems and value chains. | Lecture 2 Enterprise Systems Development (CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor CIIT College of Statistical and Acturial Science Confusion with Programs and Products Programs Software Products Usually small in size Large Author himself is sole user Large number of users Single developer Team of developers Lacks proper user interface Well-designed interface Lacks proper documentation Well documented & user-manual prepared Ad hoc development Systematic development Software Programming ≠ Software Engineering Software programming: the process of translating a problem from its physical environment into a language that a computer can understand and obey. (Webster’s New World Dictionary of Computer Terms) Single developer “Toy” applications Short lifespan Single or few stakeholders Architect = Developer = Manager = Tester = Customer = User One-of-a-kind systems Built from scratch Minimal maintenance Software Programming ≠ Software Engineering Software engineering Teams of developers with multiple roles Complex systems Indefinite lifespan Numerous stakeholders Architect ≠ Developer ≠ Manager ≠ Tester ≠ Customer ≠ User System families Reuse to amortize costs Maintenance accounts for over 60% of overall development costs Amortize >> pay back Lecture 2 Software Systems and Their Development Life Cycle Software Systems Software Systems Vs Other Engineering Artifacts Civil Engineers develop roads, bridges etc. Electrical Engineers develop circuits, chips etc. Aeronautical Engineers develop planes Software Engineers develop software systems Software Engineering Difficulties Software engineers deal with unique set of problems Young field with tremendous expectations Building of vastly complex, but intangible systems Software is not useful on its own e.g., unlike a car, thus It must conform to changes in other engineering areas Some problems can be eliminated These are Brooks’ “accidental difficulties” Other problems can . | Lecture 2 Enterprise Systems Development (CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor CIIT College of Statistical and Acturial Science Confusion with Programs and Products Programs Software Products Usually small in size Large Author himself is sole user Large number of users Single developer Team of developers Lacks proper user interface Well-designed interface Lacks proper documentation Well documented & user-manual prepared Ad hoc development Systematic development Software Programming ≠ Software Engineering Software programming: the process of translating a problem from its physical environment into a language that a computer can understand and obey. (Webster’s New World Dictionary of Computer Terms) Single developer “Toy” applications Short lifespan Single or few stakeholders Architect = Developer = Manager = Tester = Customer = User One-of-a-kind systems Built from scratch Minimal maintenance Software Programming ≠ Software Engineering
