1 / 163

Software Engineering : Construction

Software Engineering : Construction. Romi Satria Wahon o romi@romisatriawahono.net http://romisatriawahono.net +6281586220090. Romi Satria Wahono. SD Sompok Semarang (1987) SMPN 8 Semarang (1990) SMA Taruna Nusantara , Magelang (1993)

liona
Download Presentation

Software Engineering : Construction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Engineering: Construction Romi Satria Wahonoromi@romisatriawahono.nethttp://romisatriawahono.net+6281586220090

  2. Romi Satria Wahono • SD Sompok Semarang (1987) • SMPN 8 Semarang (1990) • SMA Taruna Nusantara, Magelang (1993) • S1, S2 dan S3 (on-leave)Department of Computer SciencesSaitama University, Japan (1994-2004) • Research Interests: Software Engineering,Intelligent Systems • Founder danKoordinatorIlmuKomputer.Com • Peneliti LIPI (2004-2007) • Founder dan CEO PT Brainmatics Cipta Informatika

  3. Course Contents-1- • Introduction to Software Engineering • WhatisSoftware • WhatisSoftware Engineering • Discipline andCurriculumof Software Engineering • Software Engineering Profession • Profession, Ethics and Certification • Software Industry and Market • Internet Business Model and Trends

  4. Course Contents-2- • Software Engineering Process • Software Development Life Cycle (SDLC) • Software Development Methodologies • Software Development Notation (UML) and Tools • Object-Oriented Paradigm • Software Construction • Software Construction Process: Case Study • Estimating the Size of Software Project

  5. Course Contents-3- • Software Quality Assurance • The Uniqueness of SoftwareQualityAssurance • What is Software Quality • Software Quality Factor • Software Testing • Software Engineering Research • ComputingResearch Methodology • Research Trendsin Software Engineering • Case Study: Developing Research Proposal in Software Engineering Field

  6. Software Construction

  7. Contents • Software Construction Process • Case Study: Developing Software using UML and Java • Identifying the Project Size

  8. 1. Software Construction Process: Case Study

  9. SDLC and Deliverables

  10. Planning

  11. When Do ProjectsBegin? • When someone sees an opportunity to create business value from using information technology • Then he or she creates a system request

  12. Elements of a System Request • Project Name • The name of project • Project sponsor • Primary point of contact for the project • Business need • Reasonprompting the project • Business requirements • Business capabilities the system will need to have • Business value • Benefitsthe organization can expect from the project • Special issues • Anything else that should be considered

  13. Business Need • Describes why the system should be built • Why the project should be funded • Should be clear and concise • Probably not completely defined

  14. Business Requirements • What the system will do • High level explanation to the approval committee • Tell about the features and capabilities

  15. Business Value • Tangible value • A quantifiable value • E.g.: 2 % reduction in operating cost • Intangible value • Intuitive believe why the system will help the company • E.g.: improved customer service, a better competitive position

  16. Exercise: Identify Tangible and Intangible Value Dominion Virginia Power is one of the nation’s ten largest investor-owned electric utilities. The company delivers power to more than two million homes and businesses in Virginia and North Carolina. In 1997, the company overhauled some of its core processes and technology. The goal was to improve customer service and cut operations costs by developing a new workflow and geographic information system. When the project was finished, service engineers who used to sift through thousands of paper maps could pinpoint the locations of electricity poles with computerized searches. The project helped the utility improve management of all its facilities, records, maps, scheduling, and human resources. That, in turn, helped increase employee productivity, improve customer response times, and reduce the costs of operating crews.

  17. Special Issues Identify special issues or constraints • Budget constraints • Deadline • Legal requirements

  18. Elements of a System Request

  19. Exercise: Membuat System Request • Lihatcontoh System Request untukInternet Order Project • Pikirkansuatusistem* yang saatinidibutuhkanolehperusahaanatauorganisasianda • Buat System Request darisistemtersebut * System request yang anda buat akanmenjadistudikasusdaripembelajarankitaselama course berlangsung

  20. Feasibility Analysis

  21. Feasibility Analysis Detailing Expected Costs and Benefits • Technical feasibility • Can we build it? • Economic feasibility • Should we build it? • Organizational feasibility • If we build it, will they come?

  22. Feasibility Analysis Template

  23. Technical Feasibility: Can We Build It? • Familiarity with application • Knowledge of business domain • Need to understand improvements • Need to recognize pitfalls and bad ideas • Familiarity with technology • Is technology new to this organization? • Is this a brand new technology? • Extension of existing firm technologies

  24. Technical Feasibility: Can We Build It? • Project size • Number of people, time, and features • Compatibility with existing systems • Systems are not built in a vacuum • Needs to integrate with current systems and data

  25. Economic Feasibility: Should We Build It?

  26. Cost-Benefit Analysis - Cash Flow • Project costs and benefits over several years(3–5) • Use normal growth rates for sales etc. • Total added to determine • Overall Benefits = Total Benefits – Total Costs • Higher number is better

  27. Cost-Benefit Analysis - Cash Flow

  28. Cash Flow Plan

  29. Present Value (PV) • The amount of an investment today compared to the same amount n years in the future • Taking into account inflation and time PV = Amount (1 + Interest Rate)n

  30. Net Present Value

  31. Net Present Value (NPV) The present value of benefit less the present value of cost NPV = PV Benefits – PV Costs

  32. NPV Calculation

  33. Return on Investment (ROI) The Amount of revenue or cost savings results from a given investment ROI = Total Benefits – Total Costs Total Costs

  34. ROI Calculation

  35. Break Even Point (BEP) The point in time when the costs of the project equal the value it has delivered BEP = * Use the yearly NPV amount from the first year in which project has positive cash flow Yearly NPV* – Cumulative NPV Yearly* NPV

  36. BreakEven Point (BEP)

  37. Organizational FeasibilityIf we build it, will they come? Strategic Alignment • How well does the project match up with the business strategy? Stakeholder analysis considers • Project champion(s) • Organizational management • System users • Anybody affected by the change

  38. Stakeholder Analysis Considers • Project champion(s) • High-level non-IS executive • Shepherds project to completion • It's good to have more than one • Organizational management • Need this support to sell system to organization • System users • In the loop so end system meets needs

  39. Stakeholder Analysis Considers

  40. Feasibility Analysis Template

  41. Exercise: Membuat Feasibility Analysis • Lihatcontoh Feasibility Analysis untukInternet Order Project • Perhatikankembali System Request yang sebelumnyasudahkitabuat • Buat Feasibility Analysis dari system yang akankitabuattersebut

  42. Analysis and Design

  43. System Analysis and Design with UML • System Analysis • Business Process Identification • Use Case Diagram • Business Process Modeling • Activity Diagram or Business Process Modeling Notation (BPMN) • Business Process Realization • Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) • System Design • Program Design • Class Diagram(Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) • Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) • Deployment Diagram (arsitektur software dari sistem yang dibangun) • User Interface Design (Buat UI design dari Boundary Class) • Entity-Relationship Model(Buat ER diagram dari Entity Class)

  44. Use Case Diagram

  45. Use Case • A formal way of representing how a business interacts with its environment • The discrete activities performed by the user • Use cases are logical models that describe the activities of a system • Used to document the As-Is system, or to develop the To-Be system

  46. Use Case Diagrams • Summarized into a single picture • All of the use cases for the part of the system being modeled • Use Case Diagram tells what the system will do • Good for communicating with users

More Related