[NickDMax]

Software Development Tutorial Ideas

The following is a list of ideas for tutorials for the software development tutorial section.

Setting Up a Project

• Choosing a language for your project
  
• Choosing an online Host for your project (perhaps a review of various hosts: Google, Sourceforge etc.)
  
• Source Control strategies
  
• Bug Tracking strategies
  
• Build Systems/Strategies
  
• Online Collaboration strategies
  
• Choosing a Distribution License

Project Management

• Basics of Project Management
  
• Gantt charts
  
• UML
  
• Software Development Methodologies

QA Strategies

• Unit Testing
  
• Load Testing
  
• Regression Testing
  
• Integration Testing
  
• How to Conduct a Code Review

Design Patterns

• Why and how they are used

Design Analysis

• Functional Decomposition
  
• Object Oriented Analysis

Debugging Techniques

• How to design an exception framework
  
• How to implement Logging/best practices

Please help me flesh out this list by suggesting other sections and topics that would like to see tutorials written for or you feel would be beneficial to others.

[mysticDragon]

Don't forget software maintenance.

[MentalFloss]

Quote

QA Strategies

* Unit Testing
* Load Testing
* Regression Testing
* Integration Testing
* How to Conduct a Code Review

Functional testing, smoke tests, concurrency testing, usability testing.

Also, a section on debugging techniques might be warranted. However, I only know this from the perspective of C# currently.

[NickDMax]

correct me if I am wrong but don't we have:

Function Testing covered by unit testing?
concurrency testing covered by load testing?


I have no idea what smoke tests are, and usability testing I am not sure that fits into software development proper...

[avadhesh666]

All these are very important for software development and if you use it technically it will really help.

[CasGrimes]

any news on these tutorials happening?

[KYA]

You're more then welcome to write one and then we can cross it off the list.

[CasGrimes]

KYA, on 26 August 2010 - 03:58 PM, said:

You're more then welcome to write one and then we can cross it off the list.

Nowhere near skilled enough, was hoping these were made so I can use them that's all.

[ladyinblack]

So, is this still in the pipeline, by that I mean, can we, if we want, still submit a tutorial. I remember smoke testing from my Advanced Software Development studies earlier this year. Perhaps its something new, maybe that's why you haven't heard of it, I don't know. When submitting this tutorial, are we allowed to quote from text books we used?

Oh, nevermind, found it.

This post has been edited by ladyinblack: 15 July 2011 - 05:05 AM

[rozerdun]

Can any one explain different types of software testing?

[Oak]

rozerdun, on 22 August 2011 - 12:33 AM, said:

Can any one explain different types of software testing?

OK, i'll give it a shot, not based on formal theory, but on how I try to be effective in testing and reducing testing overlap.

I classify testing according to 3 types
1. functional testing
2. integration testing
3. unit testing

Functional testing. Some may call it system testing, user acceptance test, or alpha/beta testing..
In functional testing, the focus is verifying the requirements are met, in other words, are we building the right product? So, the key input is requirements specs. Test cases are generated to verify that each and every user requirements/features are exercised. To do so, we need to be able to analyze the requirements well, meaning testable requirement specs must be available. Identifying and walking through use-cases are helpful here.

Integration testing. Objective of my integration testing is to verify the design. This test focus on ensuring the various modules making up the complete software are interacting correctly. This is important because we can have many re-used modules/libraries linked into our final code. We want to make sure we are using the modules as intended because we are assumming that the modules/libraries are implemented and tested previously. For example, a function may be defined to be executed every 10 ms and accept a certain input range. Integrating the code into a design that call the function every 5 ms may result in error. Integration test hopefully will catch this type of errors which will not be found in unit testing.

Unit testing. Objective of unit testing is verifying the implementation of the function/unit. The test cases should try to cover all the branches in the code, check for boundary conditions, ensuring error inputs are handled, etc. Unit testing checks for coding errors and robustness of implementation. Effective unit testing means the module/function should perform only one function. Unit testing techniques used in my organization include equivalence partitioning, boundary value testing, code coverage analysis using static tools. Upon completion of unit testing, we are fairly confident the module is implemented according to its design, all possible input values are exercised, and invalid values or combination are handled gracefully.

So unit testing is done after coding, followed by integration testing, and finally functional/system test. Performance measurement is therefore done at functional test as this is a customer requirement. Test cases are done according to V-model lifecycle, that means functional test cases are created after Requirements Analysis/Specification, integration test cases are created once the architecture design is done, and unit test cases should be done after unit design is completed. In practice however, this is not always strictly followed by the engineers.

So, in a nutshell,
functional testing = verify the requirements are met
integration testing = verifying the design and usage of functions
unit testing = verifying the code implementation and algorithm of functions/classes

[BobRodes]

Most software projects fail from inadequate understanding of the requirements. Requirements gathering and documentation techniques ought to be a part of this, I would think.

[developersglobal]

NickDMax, on 04 March 2010 - 08:37 AM, said:

Software Development Tutorial Ideas

The following is a list of ideas for tutorials for the software development tutorial section.

Setting Up a Project

• Choosing a language for your project
  
• Choosing an online Host for your project (perhaps a review of various hosts: Google, Sourceforge etc.)
  
• Source Control strategies
  
• Bug Tracking strategies
  
• Build Systems/Strategies
  
• Online Collaboration strategies
  
• Choosing a Distribution License

Project Management

• Basics of Project Management
  
• Gantt charts
  
• UML
  
• Software Development Methodologies

QA Strategies

• Unit Testing
  
• Load Testing
  
• Regression Testing
  
• Integration Testing
  
• How to Conduct a Code Review

Design Patterns

• Why and how they are used

Design Analysis

• Functional Decomposition
  
• Object Oriented Analysis

Debugging Techniques

• How to design an exception framework
  
• How to implement Logging/best practices

Please help me flesh out this list by suggesting other sections and topics that would like to see tutorials written for or you feel would be beneficial to others.

This post is exactly what I was looking for it is a great help!!!

Thanks,
DG