Exploring Software Engineering Processes and Prototyping Methods
"Dive into the world of software engineering processes, project outcomes, and the importance of prototyping in product development. Understand the significance of refactoring and rapid prototyping, along with the challenges and benefits they bring to the table."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
CSE 416 Product Prototyping SOFTWARE ENGINEERING
Software runs the world The economies of ALL developed nations are dependent on software. more and more systems are software controlled expenditure on software represents a significant fraction of GNP in many countries
Software Project Outcomes 2003 study of 280,000 SW Projects Successful Canceled Late, Over Budget, or Incomplete
What is the primary culprit? Faulty Requirements Engineering Planning the wrong thing Designing the wrong thing Making the wrong thing Disconnect between these stages each step requires proper discipline
We have an ambitious project Map Loading Map Viewing Map Graphics Creation Map Graphics Editing Map Graphics Viewing Map Graphics Exporting Accounts Management Content Sharing Community Interactions
Product Prototyping What s a prototype? an incomplete version of the product being developed Why do it? discovery (i.e. learn more about the problem) solve hard problems first see what works see what doesn t work get customer feedback use as a communication tool $
Rapid Prototyping Not a practical solution for some types of projects, especially those of high complexity Employed by agile development strategies Create multiple prototypes in iterative cycles may employ some design with each iteration Why? requires lots of refactoring See the product evolve with each prototype Pros: cyclical feedback, adapt product to changing needs Cons: lack of planning can lead to messy implementation
Refactoring Cascading software design changes through an implementation Example: you wish to move an instance variable from one class to another you need to move the variable and all functions that service it this may or not be easy to do Other examples: change the number of arguments in a method change a relationship from HAS-A to IS-A (or vice versa)
Typical Refactoring Motivation Improve code to employ more abstraction Example: FileLoader class in application loads a Shapefile As project progresses you also want to load GeoJSON files Make FileLoader abstract or just an interface Make ShapefileLoader implement loading of .shp/.dbf Make GeoJSONLoader implement loading of .json Have application deal with them in similar ways
For our Project We are using prototyping as forced learning solve very specific problems train the team immerse team members in formats everyone designs better the 2nd time around After this prototype we will do informed planning and then design
Next Up More Planning Use Case Modeling UI Modeling
