Archives

  • 2018-07
  • 2018-10
  • 2018-11
  • 2019-04
  • 2019-05
  • 2019-06
  • 2019-07
  • 2019-08
  • 2019-09
  • 2019-10
  • 2019-11
  • 2019-12
  • 2020-01
  • 2020-02
  • 2020-03
  • 2020-04
  • 2020-05
  • 2020-06
  • 2020-07
  • 2020-08
  • 2020-09
  • 2020-10
  • 2020-11
  • 2020-12
  • 2021-01
  • 2021-02
  • 2021-03
  • 2021-04
  • 2021-05
  • 2021-06
  • 2021-07
  • 2021-08
  • 2021-09
  • 2021-10
  • 2021-11
  • 2021-12
  • 2022-01
  • 2022-02
  • 2022-03
  • 2022-04
  • 2022-05
  • 2022-06
  • 2022-07
  • 2022-08
  • 2022-09
  • 2022-10
  • 2022-11
  • 2022-12
  • 2023-01
  • 2023-02
  • 2023-03
  • 2023-04
  • 2023-05
  • 2023-06
  • 2023-07
  • 2023-08
  • 2023-09
  • 2023-10
  • 2023-11
  • 2023-12
  • 2024-01
  • 2024-02
  • 2024-03
  • 2024-04
  • Agile methodologies introduced best practices to execute sof

    2018-10-25

    Agile methodologies introduced best practices to execute software projects. These methodologies including eXtreme Programming (XP) depend mainly on twelve basic processes [4,7]: The next section describes the initiatives of this paper. It refers to noticed problems that have been induced during the software development of business process reengineering projects. Unfortunately, organizations could not fulfill the recommendations of quality management system. The recorded reasons are the failure of plan-driven team software process methodology to execute project at a time and to response to frequent requirement changes especially in Middle East countries [9]. The literature studies have introduced solutions depending on eXtreme Programming and unique GS-9620 manufacturer method. They have also monitored effect of virtual team work on the success of project and minimization of collocation meeting costs [9].
    Background The twelve baseline practices approved their ability to respond to frequent requirement changes and to avoid frequent risk factors. The dependency on virtual team meeting such distributed pair programming and online representative customer or end user are proposed to get better results as minimizing transportation costs and allow system high availability. The proposed Virtual Team Software Process Methodology adopts eXtreme Programming and virtual team methodology to avoid restrictions of plan driven team software methodology and realize flexibility, scalability and continuous upgrade of systems [11].
    Proposed methodology Our proposed methodology depends on the assumption of high ROI of eXtreme Programming and the flatten runtime cost of change. These hypotheses refer to the effect of utilization of existing financial and technical resources of organization. Also, they depend on the deployment of available human resources and high availability of system as it is designed for self and on-job training. The adaptation of eXtreme Programming methodology is proposed to provide ability of collective ownership and pair programming practices, which minimizes training requirements, and so any new employee can be easily involved into project with low down time [16]. The adoption of architecture eXtreme Programming to match virtual team guidelines using distributed pair programming, alternative group coordination [26], online automatic documentation, and online customer representative characterize our proposed methodology, which is called “Virtual Team Software Process Methodology”. The VTSP methodology is assumed to minimize risk factors and to achieve the frequent requirement change on software development life cycle of Business Process Reengineering (BPR) project [2]. The hypothesis framework is shown (see Fig. 3). This paper refers to fuzzy logic concept to describe the input, output and processes parameters of theoretical framework. Reason to use fuzzy concept is the ambiguous level of social factors of virtual team work and the ambiguous level of practices of extreme Programming methodology. Each section is located within fuzzy region from very low to very high. We proposed decimal weight for each factor. The virtual team process methodology and ROI output of project parameters are proposed to be normalization to scales: From low levels within closed interval [0, 0.5] and high levels within closed interval [0.5, 1]. The domain of interval from [0, 1] is selected as wide spectrum to be expressible and easily evaluated [6,21]. This automatic system monitoring is implemented through our proposal terminal screen to sample 100 team members, who have authority to access and control screen. The rate of logging screen and number of active screen user indicate the ability of proposed methodology to improve the performance of each release and so global project [22]. The research follows the activity of the virtual team work and monitor the effect of their deployment of the modified practices of eXtreme programing [19]. This method recommends the development of virtual software application based on database server (e.g. Access or MySQL) [15]. The objective is to monitor the activity of members of team work on runtime [1,8]. The hierarchy of our methodology (see Fig. 4).