Abstract
In information systems development models are used to represent real and target enterprise systems. Ideally the enterprise could have two basic enterprise models – an As-Is model an To-Be model that may integrate all representations of the enterprise relevant to information systems development. Although there are many different suggested approaches how to model the enterprise, no consensus exists of what exactly should be the spectrum of model elements and corresponding to them enterprise artifacts for successful enterprise and information systems development. In this paper we propose an approach of identifying core enterprise model constituents for different systems development settings. The approach is based on the integration of professional knowledge regarding artifacts used in various systems development cases with the variations of a continuous requirements engineering framework that combines traditional requirements identification functions with additional continuous audit, monitoring and analytics activities.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
