Embed Size (px)
DESCRIPTION
Citation preview
Business Presentation
Edition for Presenting among Internet Social Networks
Slide 2
Who We Are
A strategic system engineering firm that deploys System Engineering concepts and tools into the product development cycle.
End-to-end system services -From software, hardware, network and processes to training and consulting.
A wealth of domain expertise in both the public and industrial sectors, including telecommunications, wireless networking, software, security and Public Safety radio communication systems.
Slide 3
What We Do
Build the right framework to optimize time, resources and customers satisfaction Your
Challenge
VeeShellSolution
Slide 4
The Essence of System Engineering
Concept of Operations
Requirements and Architecture
Detailed Design
Operations and Maintenance
System Verification and Validation
Integration, Test and Verification
Slide 5
Why is System Engineering important?
On time project completion
Within budget
Equipped with all the features and functionalities originally specified
To ensure YOUR projects SUCCEED
and increase your SUCCESS rate
Success =
Slide 6
"This year's results show a marked decrease in project success rates, with 32% of all projects succeeding which are delivered on time, on budget, with required features and functions; 44% were challenged which are late, over budget, and/or with less than the required features and functions and 24% failed which are cancelled prior to completion or delivered and never used….This year's results represent the highest failure rate in over a decade”
Jim Johnson, Chairman of The Standish Group
CHAOS Summary 2009 Report
C h al len g ed 32%S u ccess 44%
F ailed 24%
Slide 7
System Engineering Focus
The System Engineering process addresses these key factors for project success:
user involvement minimized scope firm basic requirements
Slide 8
System Engineering Delivers
System Engineering does not guarantee success
System Engineering DOES:
help identify issues earlier in the project schedule
improve chances for a successful project in the end
Slide 9
Project Management: Common Mistakes
The project was late. We added more people. The problem got worse.
Our requirements changed. The schedule did not. Are we headed for trouble?
We estimated risks. We put together contingency plans. Oops… we didn’t think of that one.
We submitted estimates. Management cut them in half. Next time we'll pad them.
Slide 10
Wait. There’s more!
We can get it right. Or we can finish on schedule. How do we do both?
We are out of time. But we’re not finished. Let’s take time from Testing.
The module failed Testing. We changed all the Tests. Now let’s change the requirements.
Slide 11
How many times have you heard these?
There is another way!
Slide 12
Address the “Weak Links”
Overcomes “project initiation euphoria”.
Balances optimistic and high expectations and real-world constraints is an important driver with a systematic approach at the outset to guide teams and manage expectations.
Shortens the “uncertainty curve”.
Focus on resolving uncertainty early in project development by defining the project scope and requirements, along with incremental development strategies to mitigate the risk of unreliable estimates.
Zeroes in on the right procurement formula.
Slide 13
Address the “Weak Links” cont.
What works for highway construction is not suitable for IT projects. Getting the procurement method right the first time save time, money and sets you on the road to success.
Gets the Timing Right
Every project has changes. System Engineering ensures there is verification and validation as the project evolves to maximize the chances of identifying defects early and optimizing the changes needed to avoid latency.
Slide 14
Requirements Requirements Requirements
Establishing clear requirements helps avoid these pitfalls:
Customer Dissatisfaction
Incomplete, missing, poorly written or ambiguous requirements can result in a product that does not meet all of the customers’ needs.
Wasted Resources
Incorrect requirements, or establishing requirements that are not truly needed, increases rework expenses. This also prevents maximizing reuse benefits.
Inaccurate Estimates
Requirements define the scope of the product. Without a clear handle on the scope, project estimates, schedules, and quality will suffer.
Slide 15
What can System Engineering do for you?
Meet customer needs and increase customer satisfaction
Achieve fiscal and performance objectives
Enable reuse and maximization of resources
Ensure quality and regulatory compliance
Troubleshoot problems early in the development cycle
Enhance agility and market responsiveness
Slide 16
What can System Engineering do for you? cont.
Avoid cost and time overruns
Increase productivity
Exploit market opportunities
Minimize risks
Manage subcontractors
Streamline change management
Slide 17
VeeShell Company Services
Requirements Management
System Design
System Analysis
Validation and Verification
Troubleshooting
Customer Interface
Information Management
Process Engineering
Coordination
Consulting
Training
Traditional Engineering
