Eisner, H. (2013, June), Systems Architecting and Software Architecting - On Separate or Convergent Paths?  Paper presented at 2013 ASEE Annual Conference & Exposition, Atlanta, Georgia. 10.18260/1-2--22511

\bibitem{asee_peer_22511}
  Eisner, H. (2013, June), \emph{Systems Architecting and Software Architecting - On Separate or Convergent Paths?}
  Paper presented at 2013 ASEE Annual Conference \& Exposition, Atlanta, Georgia.
  10.18260/1-2--22511

Howard Eisner.  "Systems Architecting and Software Architecting - On Separate or Convergent Paths?".  2013 ASEE Annual Conference & Exposition, Atlanta, Georgia, 2013, June.  ASEE Conferences, 2013.  https://peer.asee.org/22511 Internet.  22 Dec, 2024

\bibitem{asee_peer_22511}
  Howard Eisner.
  "Systems Architecting and Software Architecting - On Separate or Convergent Paths?".
  \emph{2013 ASEE Annual Conference \& Exposition, Atlanta, Georgia, 2013, June}.
  ASEE Conferences, 2013.
  https://peer.asee.org/22511 Internet.  22 Dec, 2024

@INPROCEEDINGS{asee_peer_22511
author = "Howard Eisner"
title = "Systems Architecting and Software Architecting - On Separate or Convergent Paths?"
booktitle = "2013 ASEE Annual Conference \& Exposition"
year = "2013"
month = "June"
address = "Atlanta, Georgia"
publisher = "ASEE Conferences"
note = {https://peer.asee.org/22511}
number = {10.18260/1-2--22511}
}

TY  - CPAPER
AB  -               SYSTEMS AND SOFTWARE ARCHITECTING –               ON SEPARATE OR CONVERGENT PATHS?                             Howard EisnerAbstract  Systems Engineering is an overall method and discipline for building large-scalesystems. It has been described as consisting of some twenty-five subordinateprocesses or an equivalent number of elements. Whatever the overall description, itis agreed that software engineering is a critical activity within the overall field ofsystems engineering. The success of our efforts at building large systems oftendepends upon how well we execute the software tasks within a systemsengineering framework. The software development issue is high on our list of areasthat require continuous improvement if we are to be successful at systemsengineering. Both systems and software engineering have methods for architecting.In the former case, there are several approaches, all of which are rather definitive,and have well-known proponents and supporters. These include DoDAF, MoDAF,Enterprise Architecting, and others. In the case of software engineering, theapproaches seem to be deep, varied and interesting, and not necessarily agreedupon. In this paper, the author provides an overview of both the fields of systemsand software architecting, looking especially for areas of possible commonality.Conclusions are set forth including the possibility of a unified approach.Recommendations follow, suggesting future actions as well as research areas.These results have direct relevance to the structure and content of curricula, currentand future, for systems and software engineering and architecting.Submitted to: Systems Engineering Division (SED)Submitted by:Dr. Howard EisnerDistinguished Research Professor, andProfessor, Engineering Management andSystems Engineering DepartmentSchool of Engineering and Applied ScienceThe George Washington UniversityWashington, DC 20052heisner@rcn.com; heisner@gwu.edu
AU  - Howard Eisner
CY  - Atlanta, Georgia
DA  - 2013/06/23
PB  - ASEE Conferences
TI  - Systems Architecting and Software Architecting - On Separate or Convergent Paths?
UR  - https://peer.asee.org/22511
DO  - 10.18260/1-2--22511
ER  -