Scenario Architecture - A Methodology to Build a Global View of OO Software System

Research output: Contribution to journalConference article

1 Citation (Scopus)

Abstract

OO software engineering (OOSE) has been a popular methodology for years; however, there are still some issues remaining unsolved: a generic mechanism for checking consistency of designs is still lacking; software has some problems resulting from process issue; and imperative engineer have a huge gap to adopt OOSE. These three issues intersect in the early analysis phase, therefore we represent a new methodology that provides a complete global view of OO software system that solve issues we identified, and uses requirements document and some analysis documents as foundation. Rules and a case study are also presented to exemplify the result of applying our methodology on both OOSE and imperative software engineering.

Original languageEnglish
Pages (from-to)446-451
Number of pages6
JournalProceedings - IEEE Computer Society's International Computer Software and Applications Conference
Publication statusPublished - 2003 Dec 16
EventProceedings: 27th Annual International Computer Software and Applications Conference, COMPSAC 2003 - Dallas, TX, United States
Duration: 2003 Nov 32003 Nov 6

Fingerprint

Software engineering
Computer systems
Engineers

All Science Journal Classification (ASJC) codes

  • Software
  • Computer Science Applications

Cite this

@article{f4cc77f720414dbe907e4723d2bdabc0,
title = "Scenario Architecture - A Methodology to Build a Global View of OO Software System",
abstract = "OO software engineering (OOSE) has been a popular methodology for years; however, there are still some issues remaining unsolved: a generic mechanism for checking consistency of designs is still lacking; software has some problems resulting from process issue; and imperative engineer have a huge gap to adopt OOSE. These three issues intersect in the early analysis phase, therefore we represent a new methodology that provides a complete global view of OO software system that solve issues we identified, and uses requirements document and some analysis documents as foundation. Rules and a case study are also presented to exemplify the result of applying our methodology on both OOSE and imperative software engineering.",
author = "Tsai, {Yiausyu Earl} and Hewijin-Christine Jiau and Kuo-Feng Ssu",
year = "2003",
month = "12",
day = "16",
language = "English",
pages = "446--451",
journal = "Proceedings - IEEE Computer Society's International Computer Software and Applications Conference",
issn = "0730-6512",
publisher = "Institute of Electrical and Electronics Engineers Inc.",

}

TY - JOUR

T1 - Scenario Architecture - A Methodology to Build a Global View of OO Software System

AU - Tsai, Yiausyu Earl

AU - Jiau, Hewijin-Christine

AU - Ssu, Kuo-Feng

PY - 2003/12/16

Y1 - 2003/12/16

N2 - OO software engineering (OOSE) has been a popular methodology for years; however, there are still some issues remaining unsolved: a generic mechanism for checking consistency of designs is still lacking; software has some problems resulting from process issue; and imperative engineer have a huge gap to adopt OOSE. These three issues intersect in the early analysis phase, therefore we represent a new methodology that provides a complete global view of OO software system that solve issues we identified, and uses requirements document and some analysis documents as foundation. Rules and a case study are also presented to exemplify the result of applying our methodology on both OOSE and imperative software engineering.

AB - OO software engineering (OOSE) has been a popular methodology for years; however, there are still some issues remaining unsolved: a generic mechanism for checking consistency of designs is still lacking; software has some problems resulting from process issue; and imperative engineer have a huge gap to adopt OOSE. These three issues intersect in the early analysis phase, therefore we represent a new methodology that provides a complete global view of OO software system that solve issues we identified, and uses requirements document and some analysis documents as foundation. Rules and a case study are also presented to exemplify the result of applying our methodology on both OOSE and imperative software engineering.

UR - http://www.scopus.com/inward/record.url?scp=0344666689&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0344666689&partnerID=8YFLogxK

M3 - Conference article

AN - SCOPUS:0344666689

SP - 446

EP - 451

JO - Proceedings - IEEE Computer Society's International Computer Software and Applications Conference

JF - Proceedings - IEEE Computer Society's International Computer Software and Applications Conference

SN - 0730-6512

ER -