한국컴퓨터정보학회논문지 (Journal of the Korea Society of Computer and Information)

  • 제17권10호
  • /
  • Pages.117-127
  • /
  • 2012
  • /
  • 1598-849X(pISSN)
  • /
  • 2383-9945(eISSN)
한국컴퓨터정보학회 (Korean Society of Computer Information)
권호 표지
DOI QR코드

DOI QR Code

PIECES 프레임워크 중심의 요구사항 정제와 우선순위 결정 전략

An Efficient Dynamic Workload Balancing Strategy

  • 전혜영 (숭실대학교 컴퓨터학과) ;
  • 변정원 (숭실대학교 컴퓨터학과) ;
  • 류성열 (숭실대학교 컴퓨터학과)
  • 투고 : 2012.08.20
  • 심사 : 2012.09.19
  • 발행 : 2012.10.31
PDF 다운로드
⟨ 이전 논문 다음 논문 ⟩

초록

급변하는 웹과 모바일 환경에서 사용자 요구사항을 효율적으로 찾아내고 올바르게 시스템에 반영하는 것은 매우 중요하다. 본 연구는 모바일 프로그램에서 사용되는 댓글, Q&A, 불편사항 신고 등의 사용자 요구사항을 기반으로 웹과 모바일 프로그램을 변경하기 위한 요구사항을 정제하고, 정제된 요구사항의 우선순위를 결정하기 위한 전략을 제안한다. 요구사항을 정제하기 위하여 소프트웨어사업선진화포럼의 표준화 방안, 기 개발된 프로그램 구성도를 활용하여 요구사항을 그룹화 하였으며, 이를 PIECES 에 맵핑하여, 정제된 요구사항이 시스템에 유효하게 반영될 수 있는지 여부를 확인하고 정제하였다. 정제된 요구사항의 우선순위를 결정하기 위하여 첫째, 소프트웨어의 구조, 요구사항, PIECES 카테고리에 상대적인 가중치를 부여하고, 둘째, 각 요구사항에 대한 통합 점수를 구하여 부문 및 전체 점수의 상대적인 값을 구한다. 제안한 기법의 가능성을 검증하기 위해서 S 대학교에서 서비스하는 모바일 애플리케이션의 변경 요구사항을 15명의 업무 관련 이해당사자에게 설문한 결과로 그 유효성을 입증하였다.

Identifying user requirements efficiently and reflecting them on the existing system is very important in a rapidly changing web and mobile environments. This study proposes the strategies to refining requirements and to prioritizing those refined requirements for changing of web and mobile application based on user requirements (e.g. mobile application comments, Q&A, reported information as discomfort factors). In order to refining the user requirements, those requirements are grouped by using the advancement of the software business of the Forum of standardization and the existing configuration-based programs. Then, we mapped them onto the PIECES framework to identifying whether the refined requirements are correctly reflected to the system in a way of valid and pure. To determine the priority of refined requirements, first, relative weights are given to software structure, requirements and categories of PIECES. Second, integration points on each requirement are counted to obtain the relative value of partial and overall score of a set of software structural requirements. In order to verifying the possibility and proving the effectiveness of proposing technique in this study, survey was conducted on changing requirements of mobile application which have been serviced at S University by targeting 15 people of work-related stakeholders.

키워드

참고문헌

  1. Ivy F. Hooks & Kristin A. Farry, "Customer-Centered Products - Creating Successful Products through Smart Requirements Management," Amacom, 2001.
  2. James C.Wetherbe & Nicholas P.Vitalari "Systems Anlysis and Design : best practices" West Publishing Company, 1994.
  3. Pressman, R. S., "Software Engineering - A Practitionerʼs Approach," McGraw-Hill, 2010.
  4. Boehm, B., & Sullivan, K., "Software economics: status and prospects," Information and Software Technology, Vol.41, No.14, pp.937-946, 1999. https://doi.org/10.1016/S0950-5849(99)00091-9
  5. Karl W., "Software Requirements," Microsoft Press, 2003.
  6. Darimont, R., & Van Lamsweerde, A., "Formal refinement patterns for goal-driven requirements elaboration," ACM SIGSOFT Software Engineering Notes, Vol.21, No.6, pp.179-190. ACM, 1996. https://doi.org/10.1145/250707.239131
  7. A.M. Zaremski and J. Wing, "Signature Matching: A Tool for Using Software Libraries", ACM Trans. on Software Engineering and Methodology Vol.4, No.2, pp.146-170, 1995. https://doi.org/10.1145/210134.210179
  8. IEEE, "IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications," IEEE Computer Society, 1998.
  9. Dardenne, A., van Lamsweerde, A., Fickas, S., "Goal-Directed Requirements Acquisition", Science of Computer Programming, Vol.20, No.1-2, pp.3-50, 1993. https://doi.org/10.1016/0167-6423(93)90021-G
  10. Van Lamsweerde, A., Goal-oriented requirements engineering: a guided tour. Proceedings Fifth IEEE International Symposium on Requirements Engineering, pp.249-262, 2001.
  11. B. Potter, J. Sinclair and D. Till, "An Introduction to Formal Specification and Z," Prentice Hall, 1991.
  12. Darimont, R., & Van Lamsweerde, A., "Formal refinement patterns for goal-driven requirements elaboration," ACM SIGSOFT Software Engineering Notes, Vol.21, No.6, pp.179-190, 1996. https://doi.org/10.1145/250707.239131
  13. A. Davis, "Just Enough Requirements Management," Dorset House Publishing, 2005.
  14. J.C.Wetherbe, N.P.Vitalari, "Systems Analysis and Design," West Publishing Company, 1994.
  15. Davis, A., Overmyer, S., Jordan, K., Caruso, J., Dandashi, F., Dinh, A., Kincaid, G., et al., "Identifying and measuring quality in a software requirements specification," Proceedings First International Software Metrics Symposium, pp.141-152, 1993.
  16. Covey, S.R., "The 7 habits of highly effective people," Rockfeller Center, 1989.
  17. Karlsson, J., and Ryan, K., "A cost-value approach for prioritizing requirements." IEEE Software, Vol.14, No.5, pp.67-74, 1987.
  18. Liu, X. F., "Software quality function deployment. Ieee Potentials," Kluwer Academic Publishers, 2000.
  19. B.G. Lee, M.S. Hwang, Y.B. L, H.H, Lee, J.M. Baik, C.K. Lee, "Design and Development of a Standard Guidance for Software Requirement Specification", Journal of KISS: Software and Applications, Vol.36, No.7, pp.531-538, 2009
  20. Jong-Cheol Shin, "Improving Requirements Spec -ification to extend Requirements Management over the Development Life Cycle", Journal of The Korea Society of Computer and Information, v.6, no.4, pp.30-37, 2001.12.
  21. Kyu-Jang Chung, "A Study on Data Modeling Technoques for Control Requirements of SPICE Reference Model", Journal of The Korea Society of Computer and Information, v.9, no.3, pp.1-6, 2004.9.