{"id":{"repo_id":"nps","oai_identifier":"oai:calhoun.nps.edu:10945/9746"},"canonical_url":"https://search.dev.ndltd.org/etd/nps/oai:calhoun.nps.edu:10945/9746","repository":{"repo_id":"nps","name":"Naval Postgraduate School","base_url":"https://calhoun.nps.edu/server/oai/request"},"display":{"title":"The design and development of a web-interface for the Software Engineering Automation System","abstract":"The Software Engineering Automation System evolved from the Computer-Aided Prototyping System (CAPS) developed in the late 1980gass and early 1990gass to help software engineers rapidly produce working prototypes for hard realtime embedded systems. As software development methods such as the waterfall and spiral methods evolved the requirement for a system to prototype products became clear. CAPS was able to meet the needs of the software engineer, allowing them to edit theproject, translate and compile the code, develop the interface, and execute the project. As the requirements change and customergass needs become clearer, the ability to rapidly change the prototype to meet these needs was met by the CAPS system. Today companies that are developing software systems are global in nature. Development could take place over a vast expanse of several continents. The change in the workplace environment bore the requirement to redesign SEAS to make it accessible globally as well as making it functional across multiple platforms. The envisioned redesign of the SEAS system takes the functionality of the current system and deploys it as a web application on the Internet.","abstract_html":"The Software Engineering Automation System evolved from the Computer-Aided Prototyping System (CAPS) developed in the late 1980gass and early 1990gass to help software engineers rapidly produce working prototypes for hard realtime embedded systems. As software development methods such as the waterfall and spiral methods evolved the requirement for a system to prototype products became clear. CAPS was able to meet the needs of the software engineer, allowing them to edit theproject, translate and compile the code, develop the interface, and execute the project. As the requirements change and customergass needs become clearer, the ability to rapidly change the prototype to meet these needs was met by the CAPS system. Today companies that are developing software systems are global in nature. Development could take place over a vast expanse of several continents. The change in the workplace environment bore the requirement to redesign SEAS to make it accessible globally as well as making it functional across multiple platforms. The envisioned redesign of the SEAS system takes the functionality of the current system and deploys it as a web application on the Internet.","abstract_has_math":false,"creators":["McDonald, James A."],"institution":null,"degree_name":null,"degree_level":null,"degree_discipline":null,"degree_department":"Computer Science","school":null,"contributors":[],"advisors":["Shing, Man-Tak","Riehle, Richard"],"committee_chairs":[],"committee_members":[],"year":2001,"date_issued":"2001-09","date_published":"2001-09","updated_at":"2026-07-27T20:25:20Z","subjects":[],"languages":[],"rights":["This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States."],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"https://hdl.handle.net/10945/9746","outbound_label":"Handle","outbound_source":"dc:identifier.uri"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor.advisor","label":"Advisor","values":["Shing, Man-Tak","Riehle, Richard"]},{"key":"dc:contributor.department","label":"Department","values":["Computer Science"]},{"key":"dc:creator","label":"Author","values":["McDonald, James A."]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date","label":"Dc Date","values":["Sept 2001"]},{"key":"dc:date.accessioned","label":"Dc Date Accessioned","values":["2012-08-22T15:29:57Z"]},{"key":"dc:date.available","label":"Dc Date Available","values":["2012-08-22T15:29:57Z"]},{"key":"dc:date.issued","label":"Date","values":["2001-09"]},{"key":"dc:type","label":"Dc Type","values":["Thesis"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:rights","label":"Dc Rights","values":["This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States."]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier.uri","label":"Identifier URI","values":["https://hdl.handle.net/10945/9746"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["The Software Engineering Automation System evolved from the Computer-Aided Prototyping System (CAPS) developed in the late 1980gass and early 1990gass to help software engineers rapidly produce working prototypes for hard realtime embedded systems. As software development methods such as the waterfall and spiral methods evolved the requirement for a system to prototype products became clear. CAPS was able to meet the needs of the software engineer, allowing them to edit theproject, translate and compile the code, develop the interface, and execute the project. As the requirements change and customergass needs become clearer, the ability to rapidly change the prototype to meet these needs was met by the CAPS system. Today companies that are developing software systems are global in nature. Development could take place over a vast expanse of several continents. The change in the workplace environment bore the requirement to redesign SEAS to make it accessible globally as well as making it functional across multiple platforms. The envisioned redesign of the SEAS system takes the functionality of the current system and deploys it as a web application on the Internet."]},{"key":"dc:title","label":"Title","values":["The design and development of a web-interface for the Software Engineering Automation System"]}]}],"canonical_facts":{"dc:contributor.advisor":["Shing, Man-Tak","Riehle, Richard"],"dc:contributor.department":["Computer Science"],"dc:creator":["McDonald, James A."],"dc:date":["Sept 2001"],"dc:date.accessioned":["2012-08-22T15:29:57Z"],"dc:date.available":["2012-08-22T15:29:57Z"],"dc:date.issued":["2001-09"],"dc:description.abstract":["The Software Engineering Automation System evolved from the Computer-Aided Prototyping System (CAPS) developed in the late 1980gass and early 1990gass to help software engineers rapidly produce working prototypes for hard realtime embedded systems. As software development methods such as the waterfall and spiral methods evolved the requirement for a system to prototype products became clear. CAPS was able to meet the needs of the software engineer, allowing them to edit theproject, translate and compile the code, develop the interface, and execute the project. As the requirements change and customergass needs become clearer, the ability to rapidly change the prototype to meet these needs was met by the CAPS system. Today companies that are developing software systems are global in nature. Development could take place over a vast expanse of several continents. The change in the workplace environment bore the requirement to redesign SEAS to make it accessible globally as well as making it functional across multiple platforms. The envisioned redesign of the SEAS system takes the functionality of the current system and deploys it as a web application on the Internet."],"dc:identifier.uri":["https://hdl.handle.net/10945/9746"],"dc:rights":["This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States."],"dc:title":["The design and development of a web-interface for the Software Engineering Automation System"],"dc:type":["Thesis"]},"updated_at":"2026-07-27T20:25:20Z"}