Selected Topic Tool based SW-Engineering

Adding files to Repository (repo)
Check out (download a file from repo)
Check in (uploading a file to repo)
Changelog/History (list of changes)
Update (load the latest version from repo) 

Branch (create a new copy of the code on repo)
Diff (finding the differences between two verisons of a file)
Merge (bringing two Branches together)
Conflict Resolution (changes have been created on one file at the same time)
Locking (prevent others to work on a file)

Local sandbox for everyone
Works offline
Fast
Branching and merging is easier

No backup
No latest version
No readable revision numbers

Req. Analysis - elicitation / documenting / formulating / managing of requirements
Design - design decisions are made, documented and verified
Implementation - coding, documentation of code, source code management, code change mgmt.
Testing - Test case definition and creation, creating test data, running tests, managing bug reports
Release - Defining dependencies, Running the tests, Building the software (automatically)
Maintenance -  how software could be changed / refactored or replaced

Req. formulation, documentation and management

Products: Microsoft Team Foundation Services, Atlassin Jira, IBM Rational DOORS

Pros: integration into IDE (VS), good collaboration and source code management

Cons: no holistic management

Pros: integration into IDE (VS), good collaboration and source code management

Cons: no holistic management

Pros: good collaboration and source code management

Cons: no IDE integration

These tools act as collaboration platforms to share ideas, thoughts and information in a team. They enable you to define workflows, layout of sites , manage content and so on.

These tools enable you to map your user stories and to generate .Net Code out of your business requirements. 

Such tools are quite good for formulating the requirements, sometimes for documentation but is hard to keep track of all the changes/to manage the requirements

A build server, also called a continuous integration server (CI server), is a centralized, stable and reliable environment for building distributed development projects. 

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day.

centralized: everybody checks in to the main trunk
distributed: everybody has his own repo and syncs to the global repo

Push: sending changes to another repo
Pull: loading a change from another repo

• Planned manual testing. Manual testing by organizing tests into test plans and test suites by designated testers and test leads.

• User acceptance testing. Testing carried out by designated user acceptance testers to verify the value delivered meets customer requirements, while reusing the test artifacts created by engineering teams.

• Exploratory testing. Testing carried out by development teams, including developers, testers, UX teams, product owners and more, by exploring the software systems without using test plans or test suites.

• Stakeholder feedback. Testing carried out by stakeholders outside the development team, such as users from marketing and sales divisions.