• Journal of KIISE
• /
• v.42 no.7
• /
• pp.878-888
• /
• 2015

Software project planning includes several processes for estimating the effort required to complete software project tasks, allocating human resources to tasks, and creating a project plan. Because software planning is becoming more complicated as the size of software projects grow, it is difficult for project managers to decide on a reasonable project plan. To help them, many automatic software project planning approaches have been proposed. The approaches all focus on minimizing project duration. But if the plan is simply to minimize the duration, without considering software quality, the plan can harm the eventual software quality. In our research to create a reasonable project plan, we consider software quality as well as duration of the project, by defining a software quality score. The project manager can plan the project to maximize software quality for a specific project duration.

• Journal of Software Engineering Society
• /
• v.26 no.4
• /
• pp.77-92
• /
• 2013

To plan a software project, the manager (1)make a work breakdown structure (WBS), (2) estimate efforts for each task, (3) assign employee to each task, and (4) estimate overall schedule. When software project becomes complicated, the possible combination of WBS, effort, and employee assignments dramatically becomes larger. Software planning tool can help software project managers to deal with this complexity. In this research, we discuss with a group of experts who work in software industry, to elicit practical requirements that should be considered in the software planning technique. Considering these requirements, we develop a software project planning tool APP (Automatic Project Planner) which provide effort estimation based on historical knowledge data and automatic human resource allocation. Our technique can be the basis of reasonable and practical software project planing.

• Journal of KIISE:Software and Applications
• /
• v.30 no.3_4
• /
• pp.293-307
• /
• 2003

Object-oriented development has been generalized, but object-oriented project planning and scheduling techniques have not been studied enough. Furthermore, it is difficult to apply the conventional software management techniques to object-oriented projects. Especially, the large scaled projects are increasing, but the project planing techniques for these large scaled projects have not been proposed enough. In this paper, we propose systematic techniques for OO based project scheduling. We suggest a 7 step-process for deriving the OO project schedule from the use-case diagram which is describing the functional requirements of the system. The proposed process includes identifying use-cases, drawing preliminary chart through interdependency analysis, identifying characteristics of each use case, determining the number of iteration, assigning use-cases to iteration, considering available resource and constraints, drawing revised PERT chart. Each step has the explanation of the input, output, and the guidelines needed to perform the step. The project scheduling technique proposed in this paper ran be used effectively in the planning phase which the purpose is to plan a development schedule to yield the high quality software in minimum time.

• International Journal of Computer Science & Network Security
• /
• v.24 no.6
• /
• pp.17-22
• /
• 2024

Software cost and schedule estimation is usually based on the estimated size of the software. Advanced estimation techniques also make use of the diverse factors viz, nature of the project, staff skills available, time constraints, performance constraints, technology required and so on. Usually, estimation is based on an estimation model prepared with the help of experienced project managers. Estimation of software cost is predominantly a crucial activity as it incurs huge economic and strategic investment. However accurate estimation still remains a challenge as the algorithmic models used for Software Project planning and Estimation doesn't address the true dynamic nature of Software Development. This paper presents an efficient approach using the contemporary Constructive Cost Model (COCOMO) augmented with the desirable feature of fuzzy logic to address the uncertainty and flexibility associated with the cost drivers (Effort Multiplier Factor). The approach has been validated and interpreted by project experts and shows convincing results as compared to simple algorithmic models.

• Korean System Dynamics Review
• /
• v.4 no.2
• /
• pp.95-130
• /
• 2003

The purpose of this study is to find what causes make public projects hold off, going beyond the planned deadline and budget. Using System Dynamics(SD) and their derivative Urban Dynamics(UD) models, it intends to analyze major feedback loops based on VENSIM and to simulate them with STELLA software, all of which are interrelated with various causes of project delay. To prevent or ameliorate project delay, first of all it advises to focus on endogenous delaying factors not exogenous ones. These factors either reinforce or balance certain loops in complex causal structure, In the case example on the Cremation Building Project in Cheongju, Residents’ participation demand make negotiation put off and delayed negotiation reinforces administrative-expediency planning in order to observe a time limit, on the other hand, once building consensus, it increase both the level of planning performance and public trust. In the meantime, the real planning process used to neglect residents opinions and manage public grievance only through compensation, he a result of simulation, visible fruit of negotiation in the initial phase seems to be not satisfactory owing to funds and time consumed, but after reaching an mutual agreement among stakeholders, planning performance is effective and strategic than administrative-expediency planning viewed in both financial and time angle. It proposes to devise specific tools schematizing project implementation. In order to upgrade the quality of project management, it recommends for planners to adopt key concepts based on SD/UD diagrams and causal loops, which would contribute to enriching Planning abbots.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.295-306
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differ from project to project. This paper suggests the criteria for effort allocation in planning, specifying, building, testing and implementing phase followed by the project total effort. These criteria are derived from 183 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

• Journal of Internet Computing and Services
• /
• v.19 no.2
• /
• pp.43-48
• /
• 2018

Various artifacts that are produced as software R&D project progresses contain research plan, research report, software requirements and design descriptions, etc. When conducting a software R&D project, it is necessary to confirm that the developed system has implemented its research requirements well. However, various research results make it difficult to design appropriate tests. So, there is a practical need for us to comprehensively handle the planning, execution, and reporting of software test for finding and verifying information related to the research. In this paper, we propose a useful method for software test process in R&D project which supports model based software testing. The proposed method supports automation of test design and generation of test data by explicitly separating each step of System Under Test (SUT). The method utilizes the various models representing the control flow of the function to extract the information necessary for testing the system. And it supports a systematic testing process based on TMMi and ISO 29119. Finally, we show the validity of the method by implementing a prototype with basic functionality to generate test data from software behavioral models.

• Industrial Engineering and Management Systems
• /
• v.10 no.1
• /
• pp.43-53
• /
• 2011

Currently, knowledge within the field of software development is largely implicit and is not formally disseminated and shared. This means that there is little improvement and regeneration of processes, and knowledge gained from previous projects is not necessarily applied to new ones. In order to turn this situation around it is necessary to take an organized approach to sharing job-related information. For this study, the authors constructed "Amalab-Project Planning Navigation System, or A-PPNS", a system for organizing accumulated knowledge related to the field of software development. More specifically, A-PPNS is a business process monitoring system and consists of the following four elements: (i) Optimized estimate support subsystem, (ii) Schedule monitoring system, (iii) QCD optimization diagnostic system, and (iv) Strategic technology accumulation system. The effectiveness of this system has been demonstrated and verified at Company A, a system integration company.

• Journal of Construction Engineering and Project Management
• /
• v.1 no.3
• /
• pp.18-27
• /
• 2011

Although information communication technology (ICT) is long regard as very useful tool in today's construction engineering and project management environment, organizations must not only operate based upon its original setting, but also requires on-going observation, additional features and fine-tuning actions before the desirable outcome can be achieved. However, it is a very common phenomenon that organizations purchase the licensed "off-the-shelf-software" package and customize it to suit their own business need. Due to the incapability of such software and inefficient customization, the possible result is making that ICT tool not user-friendly and sometimes the whole system becomes obsolete. The purpose of this paper is to review and report those actions taken (between February 2006 and December 2010) by a construction organization to enhance the performance of its Enterprise Resource Planning (ERP) system launched in December 2002. Such actions include: improving data inputting method; removing the transition bottleneck; introducing crystallization function; revising the organization's "Delegation and Limits of Authority"; publishing the "League Table" amongst users; integrating the 3D Mode into the system and upgrading hardware. Whilst the ultimate goals of such system are well beyond the time limit of this research study, an obvious interim result, achieved by this case studied organization, was winning a landmark project worth US$500 million after the ERP system was functioned properly and effectively. Their experience and success becomes an exemplar which can be borrowed by those companies, from managerial perspectives and as a roadmap, planning to adopt information technology (IT) strategy and use ICT tool in the construction engineering and project management framework. Singapore, where public housing provisions have been a major concern of their citizens as the building stock gets older.

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.865-876
• /
• 2002

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort varies according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differs from one project to another. This paper suggests models for effort allocation in planning, specifying, building, testing and implementing phases followed by the project size and development types. These models are derived from 155 different projects. Therefore, these models can be considered as a practical guideline in management of project schedule and effort allocation.