Report on Software Developing Tools

Added on -2020-02-18

| 13 pages| 4511 words| 31 views

Trusted by 2+ million users,
1000+ happy students everyday

Showing pages 1 to 4 of 13 pages

Running head: TOOLS FOR SOFTWARE DEVELOPMENTTools for software developmentName of the student:Name of the university:Author Note
1 TOOLS FOR SOFTWARE DEVELOPMENTExecutive SummaryThe report is prepared to demonstrate the software developing tools along with the background of the challengesoriginating from it. It has also reviewed various previous studies along with its analysis and discussions. Lastly the Agilesoftware is reviewed an instance of the team based software tool.
2 TOOLS FOR SOFTWARE DEVELOPMENTTable of Contents1. Introduction:.......................................................................................................................................................................32. Introduction of the recent challenges of team-based software development:....................................................................32.1. Challenges of team-based software development:.....................................................................................................32.2. The background of the identified challenges:............................................................................................................43. Reviewing of the previous studies, analysis and discussions:...........................................................................................53.1. The prior studies:........................................................................................................................................................53.2. The personal analysis:................................................................................................................................................63.4. The discussions:.........................................................................................................................................................74. Reviewing the relevant software:.......................................................................................................................................75. Conclusion:........................................................................................................................................................................96. References:.......................................................................................................................................................................11
3 TOOLS FOR SOFTWARE DEVELOPMENT1. Introduction: The complexity of the current software development has been on rise. Thus the sophisticated systems areneeded to be developers by the developer’s team [1]. The following report is prepared exploring the various practices of the software development that are team-based. It also identifies the tools that are needed to be utilized in the industry. The report has introduced the software developing tools along with the background of the recognizedchallenges. Then it has reviewed the previous studies along with its analysis and discussions. Lastly the Agilemethodology as the relevant software tool is reviewed here. 2. Introduction of the recent challenges of team-based software development:2.1. Challenges of team-based software development:The challenges are described hereafter. Feature teams versus the component teams:The feature teams has been generally assuming that the end-to-end liabilities in any system provided is done bythe orienting the work across features or stories. The component teams on the other hand have been focusing more overthe delivery of the sub-systems interacting with the sub-systems. This is done to be more useful. Because of the focus onthe delivery of the tangible value to the end-clients, the agile approaches have been favoring the feature teams over thecomponent teams [2]. However they have not necessarily been denying the necessity of possessing the component teams.There has been a common statement that is frequently heard among the technical leads and the project managers. Thisstates that they have been told that having the component teams in the agile world has not been good, that have not beenresponsible end-to-end [3]. Despite all this, in the context of the platform development there has been necessity for theassimilation of the both. For instance various services, particularly the backend ones, have been so costly andfundamental that they have needed the dedicated component group. This is against the maintaining by the feature team asthe portion of the current project.

Found this document preview useful?

You are reading a preview
Upload your documents to download
or
Become a Desklib member to get accesss

Premium

$45

Q&A Library Access

Chat support

12

Document Unlocks

4

Answer Unlocks

Students who viewed this