Embedded Files
The Software Development Cycle forms the main content of the HSC Couse. It is split into five main sections, each themselves divided into components. These links take you to more detailed pages
9.2.1 Defining and Understanding the Problem
9.2.2 Planning and Designing software solutions
9.2.3 Implementing Software Solutions
9.2.4 Testing and evaluating software solutions
9.2.5 Maintaining software solutions
In order for students to be able to develop software to meet an identified need, they first need to be able to understand the specifications of a problem so that they can eventually translate these specifications into code.
As well as having good technical skills, it is necessary for students to have good communication skills so that the users’ requirements can be fully understood and implemented throughout the development process.
The modelling tools used should conform to those specified in the Software and Course Specifications document and should provide documentation that can be interpreted by developers and maintainers.
Students should develop and refine skills as an integrated part of developing their software solutions.
It is important at this initial stage of the process that all relevant social and ethical issues are considered as an integral part of the design and development of the solution.
A short summary of a system devlopment cycle can be found below.
1. Planning
The most important parts of Software Development, requirement gathering or requirement analysis are collected from a client because the project team understands what the client wants.
2. Analysis
Defining project goals as functions. Then a development team determines what operations the intended application should have. Analysis gathers and interprets facts, and diagnosing issues with the system and recommended issues. The team then determines where obstacles lie and identifies ways to fix them.
3. Design
The requirements in design the SRS (software requirements specification) dictate the design approaches that are included in a design document specification (DDS). This is determined based on their feedback which consist risk assessment, market research, design modularity, budget, and time constraints must all be taken into consideration.
4. Implementation
The start of the actual development while the team builds a project to match the DDS. It is important to follow the coding guidelines using various programming tools like interpreters, debugging, and compilers to generate the code alongside with high-level languages like C, C++, Java and more.
5. Testing and Integration
This stage of the project is testing the environment to check errors, bugs and other issues. During the testing phase, the project is checked to ensure that defects are reported, tracked, fixed and tested again until the product meets its standards. Testing involves asking questions such as:
Does the new system meet its requirements and objectives?
Is it reliable?
Are there any remaining bugs
Does it function according to approved functional requirements?
6. Maintenance
After the product's release, maintenance is carried out for the customer. The team makes software improvements or change requests as needed. The ultimate goal of the maintenance phase is to ensure that the product remains relevant and high quality. It involves ongoing evaluations of the system's performance.
Page updated
Report abuse