{"title":"Workshop on Service Oriented Architecture","authors":"Toshiro Takase","doi":"10.1109/APSEC.2007.103","DOIUrl":"https://doi.org/10.1109/APSEC.2007.103","url":null,"abstract":"This workshop focuses on Service Oriented Architecture (SOA). Service oriented architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. By following service oriented architecture, a computer system or software is componentized as a service. One of the most important points of service oriented architecture is interoperability; the services should be accessed from other services easily. Service oriented architecture is still an emerging approach. There have not been so many concrete implementations yet. More researches and practices are required in this area.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"45 1‐10","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120861092","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Enterprise Assets Security Requirements Construction from ESRMG Grammar based on Security Patterns","authors":"K. Supaporn, N. Prompoon, Thongchai Rojkangsadan","doi":"10.1109/APSEC.2007.50","DOIUrl":"https://doi.org/10.1109/APSEC.2007.50","url":null,"abstract":"One of the highest priorities of system requirements needed in software development industry is security requirements. However, to identify the complete and correct software security requirements are a challenging task especially creating enterprise assets security requirements. Enterprise assets security requirements are to identify security basic needs, to assess risks, to establish security approach and service, and to specify external enterprise consideration including confidentiality, integrity, availability, and accountability concerns. Moreover, these may be applied to other security requirements such as identification and authentication, access control, firewall architecture, etc. Security patterns may be used to create this security requirements but understanding, analyzing and transforming from security patterns to security requirements are difficult to accomplish. We proposed a grammar, called ESRMG (enterprise security and risk management grammar), and a prototyping tool based on security patterns in a scope of enterprise asset identification and risk managements which are the fundamental of enterprise security requirements. The proposed grammar and tool are beneficial for any organization to construct enterprise security requirements and may help reduce cost and time in overall of system development.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123130869","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Kouji Aoyama, Takanori Ugai, Shigeru Yamada, A. Obata
{"title":"Extraction of viewpoints for eliciting customer's requirements based on analysis of specification change records","authors":"Kouji Aoyama, Takanori Ugai, Shigeru Yamada, A. Obata","doi":"10.1109/APSEC.2007.54","DOIUrl":"https://doi.org/10.1109/APSEC.2007.54","url":null,"abstract":"Eliciting customer's requirements is the most important issue for a system integration project. Failure to elicit the customer's requirements can cause an enormous correction cost. However there are only a few practical, concrete guidelines to do. In this paper, we describe a method to extract viewpoints and checklists for eliciting customer's requirements more effectively based on analyzing specification change records. The flow of the method is 1) representing the records in an easy-readable format, 2) identifying the causes and the phases, 3) categorizing them, 4) putting a name to a category, namely a viewpoint and 5) deriving check-items for each viewpoint. We applied the method to 135 records from 4 system development cases, and we derived 39 check-items in total. We found 78% of the specification change cases could have been prevented by only 10 check-items of requirements elicitation process. This result shows that the proposed method works effectively to extract the viewpoints for eliciting customer's requirements.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123501786","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Checking Distributed Programs with Partially Ordered Atoms","authors":"H. F. Li, E. Maghayreh","doi":"10.1109/APSEC.2007.32","DOIUrl":"https://doi.org/10.1109/APSEC.2007.32","url":null,"abstract":"Monitoring and checking the execution of a distributed program incur significant overhead due to the large number of states that need to be considered. This paper addresses two important aspects in tackling this problem: (a) atomization of the events that occur in a run, and (b) exploiting partial order semantics rather than interleaving semantics. Atomization is used to simplify analysis by compressing the events of an execution into a much smaller number of atoms. Partial order semantics promotes separation of concerns in modeling and checking program requirements involving (i) the necessary ordering among the atoms and (ii) the correctness of each atom. Ordering requirement is modeled by a set of recurrent sequences while computation requirement is modeled by a predicate that should be satisfied in the minimal state of each atom. A partially-ordered multi-set (pomset) model is presented to demonstrate the effectiveness of the approach. It is shown that property checking can be done without involving all the states of a run, regardless of the generality of the predicate involved.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128898432","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The First International Workshop on Management and Economics of Software Product Lines (MESPUL07)","authors":"M. Babar, Makoto Nonaka","doi":"10.1109/APSEC.2007.90","DOIUrl":"https://doi.org/10.1109/APSEC.2007.90","url":null,"abstract":"The first international workshop on management and economics of software product lines will bring together researchers and practitioners from academia, industry and governments to report and discuss the challenges and opportunities of adopting and managing software product lines from managerial, organizational, and economics point of view.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130085942","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Quantitative Analysis of Value-Based Software Processes Using Decision-Based Stochastic Object Petri-Nets","authors":"R. Yin, Hao Hu, Jidong Ge, Jian Lu","doi":"10.1109/APSEC.2007.78","DOIUrl":"https://doi.org/10.1109/APSEC.2007.78","url":null,"abstract":"The value-based software process (VBSP) is gaining more and more attention. However, the quantitative analysis techniques for VBSPs could not closely follow up the fast developing paces of the modeling techniques. In this paper, we proposes a decision-based stochastic extension of object petri nets (OPN) to resolve the issues. OPNs are well suited for modeling VBSPs and stochastic object petri nets (SOPN) combine the benefits of OPNs and the stochastic theory. The decision-based stochastic object petri net (DB-SOPN) model is economics driven and links value creation with decision making, multi-stakeholder satisfying, and risk management. It includes two levels: the high level models the guideline of the software process life cycle; and the low-level represents the different stakeholder's perspectives of the process. Some activities of a process have candidate policies that will produce different value reward. Our model simulates the entire software process, and compares various combinations of candidate policies to make the value reward of the process maximum.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134171542","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Use of Agile Methods and Practices in the Philippines","authors":"R. Sison, T. Yang","doi":"10.1109/APSEC.2007.98","DOIUrl":"https://doi.org/10.1109/APSEC.2007.98","url":null,"abstract":"Agile methods are increasingly gaining attention in many developed countries; however, there is a dearth of empirical studies showing their successful use in developing nations. This needs to be addressed because most software offshore outsourcing destinations are in the developing world. This paper describes experiences in the use of agile methods and practices by software development firms in the Philippines, a developing country that has consistently appeared in lists of top software outsourcing destinations. The results tend to confirm those found in the literature concerning the positive impact of agile methods on software development, and how software organizations tend to adapt agile practices to suit their own organizational and project contexts. One case study in this paper also describes a particular approach to agile offshore software development.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"208 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114144870","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Zhedan Pan, Hyuncheol Park, Jongmoon Baik, Ho‐Jin Choi
{"title":"A Six Sigma Framework for Software Process Improvements and its Implementation","authors":"Zhedan Pan, Hyuncheol Park, Jongmoon Baik, Ho‐Jin Choi","doi":"10.1109/APSEC.2007.13","DOIUrl":"https://doi.org/10.1109/APSEC.2007.13","url":null,"abstract":"Six Sigma has been adopted by many software development organizations to identify problems in software projects and processes, find optimal solutions for the identified problems, and quantitatively improve the development processes so as to achieve organizations' business goals. A Six Sigma framework for software process improvements is needed to provide a standard process and analysis tools for Six Sigma project executions, and also provide a platform for collaborations with other process improvement approaches, such as PSP/TSP and CMM/CMMI. However, few frameworks have been proposed to support Six Sigma project executions. Most of Six Sigma projects for software process improvements have been performed in an ad-hoc way. In this paper, we propose a framework to support Six Sigma projects for continuous process improvements for software developments. Based on this framework, we implemented a web-based tool, called SSPMT integrated with a software project management tool and a PSP supporting tool. The suggested framework and SSPMT is beneficial in initiating and executing Six Sigma projects, facilitating data collection and data analyses by Six Sigma toolkits, and standardizing the Six Sigma project execution process so as to achieve Six Sigma project goals and of organizations' business goals.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125412902","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Injecting security as aspectable NFR into Software Architecture","authors":"H. Bagheri","doi":"10.1109/APSEC.2007.65","DOIUrl":"https://doi.org/10.1109/APSEC.2007.65","url":null,"abstract":"Complexity of the software development process is often increased by actuality of crosscutting concerns in software requirements; moreover, software security as a particular non-functional requirement of software systems is often addressed late in the software development process. Modeling and analyzing of these concerns and especially security in the software architecture facilitate detecting architectural vulnerabilities, decrease costs of the software maintenance, and reduce finding tangled and complex components in the ultimate design. Aspect oriented ADLs have emerged to overcome this problem; however, imposing radical changes to existing architectural modeling methods is not easily acceptable by architects. In this paper, we present a method to enhance conventional software architecture description languages through utilization of aspect features with special focuses on security. To achieve the goal, aspectable NFRs have been clarified; then, for their description in the software architecture, an extension to xADL 2.0 [E.M. Dashofy, 2005] has been proposed; finally, we illustrate this material along with a case study.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"82 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116471819","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Enhancing the ESIM (Embedded Systems Improving Method) by Combining Information Flow Diagram with Analysis Matrix for Efficient Analysis of Unexpected Obstacles in Embedded Software","authors":"Yasufumi Shinyashiki, Toshiro Mise, Masaaki Hashimoto, Keiichi Katamine, Naoyasu Ubayashi, Takako Nakatani","doi":"10.1109/APSEC.2007.49","DOIUrl":"https://doi.org/10.1109/APSEC.2007.49","url":null,"abstract":"In order to improve the quality of embedded software, this paper proposes an enhancement to the ESIM (embedded systems improving method) by combining an IFD (information flow diagram) with an Analysis Matrix to analyze unexpected obstacles in the software. These obstacles are difficult to predict in the software specification. Recently, embedded systems have become larger and more complicated. Theoretically therefore, the development cycle of these systems should be longer. On the contrary, in practice the cycle has been shortened. This trend in industry has resulted in the oversight of unexpected obstacles, and consequently affected the quality of embedded software. In order to prevent the oversight of unexpected obstacles, we have already proposed two methods for requirements analysis: the ESIM using an Analysis Matrix and a method that uses an IFD. In order to improve the efficiency of unexpected obstacle analysis at reasonable cost, we now enhance the ESIM by combining an IFD with an Analysis Matrix. The enhancement is studied from the following three viewpoints. First, a conceptual model comprising both the Analysis Matrix and IFD is defined. Then, a requirements analysis procedure is proposed, that uses both the Analysis Matrix and IFD, and assigns each specific role to either an expert or non-expert engineer. Finally, to confirm the effectiveness of this enhancement, we carry out a description experiment using an IFD.","PeriodicalId":273688,"journal":{"name":"14th Asia-Pacific Software Engineering Conference (APSEC'07)","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-12-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126905794","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}