Compact 2013 Ebook

4.2 Development Process
Created by sphung on 7/11/2013 5:52:58 PM

Development Process

In this section, we will take a high level view to the overall development environment, showing the process to bring a compact 2013 device to production.

Although the objective for the content in this book is intended to help software developer to learn about Compact 2013 OS design and application development, knowing the overall development process is helpful in learning and engaging in Compact 2013 development, especially for entry level developer and application developer from the IT, Web and Mobile markets.

Different from the embedded and specialized purpose device development environment, developers working on application for the desktop client OS, Server, Web and Mobile devices don’t need to concern about the hardware design, servicing and supporting proprietary hardware in the field.

 

There are multiple phases each involves different hardware and software development tasks to bring a Compact 2013 device from concept to production, where some of these tasks are dependent on resources and results from each other.

In figure 4.1, the flowchart shows the overall hardware and software development process to bring a Compact 2013 device from concept to production.

Development-Process-FlowChart-w

Figure 4.1:  Compact 2013 device development process

The flowchart in figure 4.1 provides a general view to the overall development process, with separate tracks for hardware and software, in 6 different phases.  The flowchart represents a hypothetical project, for demonstration purpose, which may not accurately reflect all real world projects.  Depending on the size and complexity of the project, development tasks for some or all of the phases in the flowchart may be performed by a small team or multiple large teams that involves multiple departments and companies.

Let’s take a look each of the 6 development phases:

1.       For the 1st phase, the development process begins with a set of design specification for both hardware and software tracks.

2.       In the 2nd phase, the hardware team needs to find a hardware platform with all of the required functions that meets the cost target.  As the hardware team identified the hardware, they need to work with the software team to insure the necessary boot loader, board support package and device drivers are available, or can be created. 

Note:              If the software team cannot find or develop the necessary software components to support the hardware, the hardware team needs to find another platform.

3.       In the 3rd phase, both the hardware and software development teams need to work together to deliver proof-of-concept devices, to validate the design is achievable and provide functional devices for their business team to perform market research and start cultivating business for the new device.  In this phase, the hardware, software and business development teams need to work together to identify area that need improvements (Comparing to existing devices), digest feedback from customers and market research to create new function and feature for the device.

Note:              For many projects, the proof-of-concept phase is an important pivotal phase, where the business management team or venture capital funding entity makes their decision to support the project.

4.       In the 4th phase, after proof-of-concept is done, with positive result from market research and support from business management (or venture capital) to move forward, both the hardware and software teams need to work together to deliver a device that meet production requirements.

Note:              In this phase, the focus is now shifting to cost, logistic and delivery schedule.

5.       In the 5th phase, after a production quality device is achieved, the device is subject to regulatory testing and certification that are mandated by the targeted industry and distribution region, to insure the device meets the required function, performance and safety standards.

Note:              This is a critical phase, where failing regulatory testing and certification may require major redesign, and potentially can cause the project to fail.  Development team that set their focus heavily on cost reduction early on in the development process and use least cost components without considering these regulatory test and certification requirements, is likely to have problems during this phase.

6.       In the final phase, to bring the device into mass production, the hardware, software and logistic support teams need to come together to create deployment, post-delivery service and support plans, needed by to properly serve and support current and future customers.

An efficient and effective development environment, along with the right technology, are important factors that can help streamline the development process, enabling development team to act, adjust and fine-tune their development tasks to meet unexpected challenges and increase the likelihood to successfully complete the assigned project.

print

Click here to provide feedback and input

  Comments


Turkish porno izle video site in rokettubeporno izle