Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO

“We are a nationwide chain of vineyards, dedicated to producing the only the highest quality wine grapes and wine varieties.”

Software Program Needs to Track: Chemical/fertilization schedule Water levels/soil moisture content PH levels Equipment maintenance Budgeting and finances Input/output Questions From Pooginook Is it possible to create a customized program? How does one find a reliable source to develop the software? What will be the cost? Will software training be needed? Pros and cons of a customized product vs. standardized product? Is there currently a program on the market that will meet the needs?

Can be compared to Software Engineering Combination of Marketing, and Computer Software Software Requirement Analysis Multiple divisions HR Finance Marketing Crisis Management Etc. “…software product planning is critical to the development success and absolutely requires knowledge of multiple disciplines” -Alan M. Davis User Need Software Product

Definintion: Structure imposed on the development of a software product. Also known as Software Development Life Cycle (SDLC)

Agile Cleanroom Iterative Rapid Application Development (RAD) Spiral Rational Unified Process (RUP) Waterfall Extreme Programming (XP) Scrum

Differing philosophy Differing models for differing projects

RequirementsDesignImplementationVerificationMaintenance 3. Implementation 5. Maintenance 1. Requirements 4. Verification 2. Design Steps to implement a Waterfall Model:

Testing is inherent of every phase for this method Oldest used paradigm The waterfall method is an enforced discipline approach Incorporates iteration directly It is document driven Customer only sees the working version BENEFITSDRAWBACKS

“Lightweight” method Family of development processes

Each iteration passes through the full development cycle Lack of documents leads to scrutinizing Emphasizes face-to-face communication Completing in a specific time frame, or budget, is difficult Short time to develop software, incremental BENEFITSDRAWBACKS

Kent Beck, 1996 Plan the project work based on 3 techniques User stories Time frame Prioritization Build the product based on user stories and show the evolving product to the customer as soon as possible What the customer needs today Codes are written in pairs Shared ownership of the code

Stresses customer satisfaction Team work is emphasized Improves software project in 4 ways: Communication Simplicity Feedback Courage

“Incremental” method Use of iterations For each iteration, design modifications are made and new functions are added “Daily builds” When to use Most of the requirements are known early, but still expected to evolve Get basic functionality to the market early New technology

Develop the major functions first Requires early definition of a complete and fully functional system to allow definition of increments Customers can respond to each build Requires good planning and design Can re-architect within limits to accommodate new functionality May build too many features to use StrengthsWeaknesses

Pros Fast development Involves iterative development Emphasis on creating prototypes Facilitates maintenance Compromises functionality Compromises performance Cons