• 국제학술발표논문집
• /
• The 8th International Conference on Construction Engineering and Project Management
• /
• pp.243-248
• /
• 2020

In addition to a range of H&S documentation, a range of actions, beliefs, interventions, practices, and states are important in terms of achieving optimum construction H&S. Conclusions include that H&S documentation facilitates and assists planning, organising, leading, controlling, and coordinating H&S. Furthermore, current H&S documentation: is inappropriate in that it can be complex, generic, lengthy, onerous, repetitive (duplicative), and vague; engenders dubious practices; generally, 'does not add the potential value'; shifts the focus from the physical process, and could be improved. Recommendations include: industry associations should review their 'audit system' to interrogate the allocation of points; H&S documents must reflect the intention of the requirement; the synergy between H&S documentation, and actions, interventions, and practices should be investigated, digested, and focused upon, and 'audits', or rather inspections, should focus more on the physical process, actions, interventions, and practices, than documentation.

• 한국콘텐츠학회논문지
• /
• 제8권5호
• /
• pp.61-71
• /
• 2008

서술 지향적인 방법에 의한 요구사항의 도출은 명확한 요구사항을 정의하는 데 있어서 불충한 것으로 지적되곤 한다. 이것은 요구사항을 기술하는 작업자들이 시스템을 이해하는 관점에 차이가 있기도 하지만, 내용의 표현방법이나 다루는 내용의 깊이, 그리고 이러한 내용을 문서화하는 방법에 있어서도 큰 차이를 갖기 때문이다. 본 연구는 이와 같이 서술적인 방법으로 도출된 GOLORY(GLObal Resource management sYstem)의 요구사항을 개선하기 위하여 UML 기반의 다이어그램을 이용한 요구사항 분석기법을 적용한 사례이다. 특히 다이어그래밍 기법을 활용함으로써 요구사항을 체계적으로 명확하게 도식화 하고, 이를 통해 요구사항의 일관성 유지와 아울러, 중요한 요구사항의 누락 방지 등의 성과를 달성할 수 있었다.

• 해양환경안전학회:학술대회논문집
• /
• 해양환경안전학회 2018년도 공동국제학술발표회
• /
• pp.168-168
• /
• 2018

• 한국정보통신학회:학술대회논문집
• /
• 한국해양정보통신학회 2006년도 춘계종합학술대회
• /
• pp.569-572
• /
• 2006

본 논문에서는 RSS 포맷으로 제공되는 문서를 사용자가 수집하고 구독할 수 있는 RSS 리더기를 설계하기 위한 요구사항 추출과 기록을 위한 분석 모델을 제시하고자 한다. 분석모델로서는 유스 케이스 모델을 채택하여 요구사항 분석과 문서화를 수행하며, 요구사항의 분석의 수단으로서는 책임주도 설계방식에 기초한다. 특정한 리더기를 전제하지 않은 분석 모델은 비즈니스 모델로 이용될 수 있다.

• Journal of Information Technology Applications and Management
• /
• 제11권4호
• /
• pp.121-132
• /
• 2004

This paper surveyed 30 system designers and developers who had been participating in a project for five months to examine the usefulness of design artifacts for object-oriented system development. A set of nine requirement and design documents was selected in consideration of the IEEE guidelines. Overall the respondents appeared to agree that the artifacts were useful for system development. On the other hand, the contribution of design artifacts to maintenance was rated lower due to the frequent changes over the iterative process. Of the artifacts, considered more useful were use case specifications, UI design and operation specifications. The respondents were the most reluctant to write test cases. Designers did not like to document more details in the design artifacts than did developers. A future study is required to determine the economics end change management of documentation.

• 통상정보연구
• /
• 제12권4호
• /
• pp.405-427
• /
• 2010

This legal study is to compare the Electronic Transactions Act in Thailand(hereinafter 'ETA') with mainly other countries electronic transactions acts, such as UNCITRAL MLEC, UECIC, VETA, UCITA and Korea' Electronic Transactions Act The ETA is consisted of 6 chapters which included preamble and definitions. Each chapter's main point as follows. Preamble is related to the name, time of legal effect, scope and definitions. Chapter 1 is not only general principles of electronic transactions, required restriction in addition to specify the limit of application, documentation, evidential weight in reference to the data message, but also the conditions of offer and acceptance through data message, time and place of dispatch and receipt of data message, certification between origination and addressee. According to media-neutrality and the effectiveness security requirement of data message under the information system, legal certification is related to the exchange's declaration of intention, define about origination-addressee of data message. Chapter 2 is composed to provide expressly about the effectiveness security in electronic signature. Those contents are to compare the MLEC, UECIC and Electronic Transactions Act in Korea. Chapter 3 is related to legal definitions that present legal requirement about service relating electronic transaction which contents accept domestic law, the adequate requirement as eligibility, satisfied matter, self-reliance ratio of finance and other detail standard Chapter 4 is deal with the transaction which are public sector and those application requirements. And also this chapter are composed regulations about direct-indirect purpose of Thailand domestic electronic government.

• 시스템엔지니어링학술지
• /
• 제9권1호
• /
• pp.13-23
• /
• 2013

Operational Concept Descriptions or Document(OCD) shall be developed to understand stakeholder's desire for to-be-delivered system. But there is little study on methodology of OCD generation and many developers do not understand importance of OCD in Korea. According to Nicole Roberts' industry(18 U.S. companies and organizations) survey, only 30% of system development projects had OCD, too. Researchers and developers have opposing views regarding the generation of an OCD. Many researchers believe that the development and use of operational concepts at the start of large projects is essential. Alternatively, developers may view the OCD as a burden to the development process rather than an enabler due to the extensive documentation requirement. In this paper a couple of OCD guidelines were investigated to clarify how to build a CONOPS effectively and what to include. Finally, OCD for rotorcraft based Personal Air Vehicle System(PAVS) was developed as a case study. In the future, a template for generating OCD appropriate to Korean environment could be proposed.

• 시스템엔지니어링학술지
• /
• 제9권1호
• /
• pp.33-45
• /
• 2013

Systems Engineering Approach was applied to the development of operator-support core management system based on the on-site operation experience and document of core management procedures, which is for enhancing operability and safety in PHWR (Pressurized Heavy Water Reactor) operation. The dissertation and definition of the system were given on th basis of investigating and analyzing the core management procedures. Fuel management, detector calibration, safety management, core power distribution monitoring, and integrated data management were defined as main user's requirements. From the requirements, 11 upper functional requirements were extracted by considering the on-site operation experience and investigating documents of core management procedures. Detailed requirements of the system which were produced by analyzing the upper functional requirements were identified by interviewing members who have responsibility of the core management procedures, which were written in SRS (Software Requirement Specification) document by using IEEE 830 template. The system was designed on the basis of the SRS and analysis in terms of nuclear engineering, and then tested by simulation using on-site data as a example. A model of core power monitoring related to the core management was suggested and a standard process for the core management was also suggested. And extraction, analysis, and documentation of the requirements were suggested as a case in terms of systems engineering.

• 한국원자력학회:학술대회논문집
• /
• 한국원자력학회 1998년도 춘계학술발표회논문집(1)
• /
• pp.335-340
• /
• 1998

In this paper a prototype of Requirement Tracking and Verification System(RTVS) for a Distributed Control System was implemented and tested. The RTVS is a software design and verification tool. The main functions required by the RTVS are managing, tracking and verification of the software requirements listed in the documentation of the DCS. The analysis of DCS software design procedures and inter(aces with documents were performed to define the user of the RTVS, and the design requirements for RTVS were developed.

• 통상정보연구
• /
• 제7권1호
• /
• pp.55-74
• /
• 2005

Recently, many enterprises have attempted to construct data warehousing systems for decision-support. Data warehouse is an intelligent store of data that can aggregate vast amounts of information. Building DW requires two important development issues:(i) DW for the decision making of business users and (ii) metadata within it. Most DW development methodologies have not considered metadata development; it is necessary to adopt a DW development methodology which develops a DW and its metadata simultaneously. Metadata is a key to success of data warehousing system and is critical for implementing DW. That is, metadata is crucial documentation for a data warehousing system where users should be empowered to meet their own information needs; users need to know what data exists, what it represents, where it is located, and how to access it. Furthermore, metadata is used for extracting data and managing DW. However, metadata has failed because its management has been segregated from the DW development process. Metadata must be integrated with data warehousing systems. Without metadata, the decision support of DW is under the control of technical users. Therefore, integrating data warehouse with its metadata offers a new opportunity to create a more adaptive information system. Therefore, this paper proposes a DW development methodology from a metadata perspective. The proposed methodology consists of five phases: preparatory, requirement analysis, data warehouse (informational database) development, metastore development, and maintenance. To demonstrate the practical usefulness of the methodology, one case is illustrated