annvilla1998 / cs-320-softwaretesting

CS-320 Software Testing

How can I ensure that my code, program, or software is functional and secure?

Ensuring that my code is both functional and secure requires a combination of the best practices, thorough testing, and ongoing vigilance. The best practice is to follow the software development life cycle. This cycle involves 6 stages:

1. Planning - clearly defining the functional requirements of my software, understanding the purpose, features, user expectation all help build a strong foundation for the development process.
2. Design - creating a solid architecture and design for my software will help save potential drawbacks with implementation, considering factors like scalability and maintainability.
3. Implementation - following the best coding practices such as proper user validation and other secure coding guidelines, enforcing readability to allow smooth peer edits, considering reusability and scalability will ensure my software is functional and secure.
4. Testing and Integration - thorough testing is essential for both functionality and security, including all unit testing, integration testing, system testing, regression testing, vulnerability assessments, penetration testing, and dynamic application security testing.
5. Deployment - user acceptance testing needs to also be completed in the development stage in order to completely sign off everything
6. Maintenance - as technology advances, languages used in projects also advance, therefore projects need to be updated and maintained regularly in order to stay functional.

How do I interpret user needs and incorporate them into a program?

Interpreting user needs and incorperating them into a program is a critical aspect of software development to ensure that the final product meets user expectations. There are many different ways to go about achieving this:

• Gather all requirements - engage with users to gather detailed requirements with things such as interviews, surveys, workshops, etc.
• Create User Stories - "As a [user], I want to [action] so that [benefit]"
• Define Acceptance Criteria - define clear acceptance criteria that outlines what must be met for the story to be considered complete.
• User Acceptance Testing (UAT) - have users test the software against their needs allowing them to use the software and provide feedback.

How do I approach designing software?

Designing software involves creating a plan that outlines how the software will meet its intended purpose while considering factors like user needs, functionality, performance, scalability, and maintainability. I would approach it by:

1. First understanding the problem which is arguably the most important step
2. Define objectives
3. Architectural design
4. Functional design
5. User interface (UI) and design (UX)
6. Data design
7. Performance
8. Security
9. Error handling
10. Testing strategies
11. Documentation