100 likes | 270 Views
Objective. Cost effective software is a product not a serviceSoftware has definitionA known starting pointA well-defined exit criteriaA process for everything in between. . The dotCom blowout has taught that you can spend several million on software and still not have product. Customer Requirem
E N D
1. Space Coast Communication Systems, Inc. Productized SoftwareServicesJohn D. Bard, Ph.D.
President
2. Objective Cost effective software is a product not a service
Software has definition
A known starting point
A well-defined exit criteria
A process for everything in between
3. Customer Requirements Often the client company fails to define requirements
“I need five computer science types starting yesterday”
Vs.
“Tasks one thru five are sufficiently defined to warrant execution“
4. Our Approach - Productized Software Services
We mature product definition with the client before the services work begins
Tools of the Trade
UML Class Diagrams, Sequence Diagrams, State Diagrams, Use Case Diagrams, Activity Diagrams, Collaboration Diagrams, Component Diagrams and Deployment Diagrams, Timing and Sizing
CASE – hundreds to choose from – needs of the project define the tool not the other way around
5. Meeting the Needs The enablers of cost effective software solutions
Experienced Team1 Development
Team developers know each other
Been there, done that many times
Want to do the job, move onto the next
A contractor wants to park on your payroll
Usually many solutions available
The latest fad language/tool is not always best
Want experience-base, proven stability, known run-time behavior and historical cost record
6. Meeting the Needs The enemies of cost effective software solutions
NIH
“Not Invented Here” syndrome
Must use only in-house resources
Often impractical, SW Eng turnover currently 11%
Project staff profiles highly non-linear
It’s our way or the highway
My kid can run a computer, writing an embedded system can’t be that difficult
Headhunters
We’ll give you a stack of “qualified” individuals tomorrow
7. Typical Projected Staff Profile During definition phase 1:1 ratio software-to-systems
During code/test phase 3+:1 ratio
System definition rarely up for that influx of S/W eng’s
Result: extended time at full staff, Herculean effort
8. Our Strengths
9. Key Benefits – Common Process From “Benefits of CMM-based Software Process Improvement (SPI)”
Carnegie Mellon Software Engineering Institute
Cost (% of median engineer labor rate) 1.1%
Productivity Gain (LOC/hour) +35%
Early Defect Detection +22%
Time to Market -19%
Post Release Defect Reports -39%
10. Key Benefits Persistence and IP Protection
As a services company we enter into “Work For Hire” agreement
As a services company we indemnify that techniques, algorithms, processes and discoveries used are free from claim, right, title or interest
As a product company we persist and protect your project in case of follow on, upgrade or maintenance
As a product company your project might benefit, i.e., make/buy decision, from existing products
11. Next Steps Evaluate your needs
Consider your options
Call for a consultation