Best writers. Best papers. Let professionals take care of your academic papers

Order a similar paper and get 15% discount on your first order with us
Use the following coupon "FIRST15"
ORDER NOW

IT 315 Final Project Part I Solution Submission Template Name: Juan Rodriguez Date: 01/19/2017 This template is a guide for you to organize your…

1 IT 315 Final Project Part I Guidelines and Rubric Overview Throughout the course, you will develop the skills required of a software architect—a role that is in high demand in the software industry. This final project resembles a typical development project of an actual software designer or software architect. You will have the opportunity to apply, practice, and receive feedback on how software systems are designed using object-orientation and Unified Modeling Language (UML) modeling. For this assessment, you will assume the role of a consultant tasked with designing a Student Information System (SIS) for a small college that offers both online and face-to-face classes. The SIS should keep track of students’ information and their course registrations. You will be provided with information about the system, its business context, and its requirements. With this information, you will need to design the software system by applying object-oriented techniques and methods and UML modeling. Specifically, the final project is divided into three different parts, which will each be submitted separately. Each part focuses on a different stage in the development process and will be completed in sequence throughout the course. Additionally, at each stage you will validate and verify your design, explain how you arrived at it, and reflect upon your process and lessons learned. Through the milestones, you will have an opportunity to gather feedback first before you submit final versions. The three final submissions are Part I: Functional Model, submitted in Module Four; Part II: Structural Model submitted in Module Six, and Part III: Behavioral Model submitted in Module Eight. In this assignment, you will demonstrate your mastery of the following course outcomes:  Apply object-oriented techniques and methods in analyzing and designing software systems  Create UML functional models that are clearly articulated, based on software system requirements  Create UML structural models that are clearly articulated, based on functional models  Create UML behavioral models that are clearly articulated, based on functional and structural models Final Project Part I Prompt The Student Information System Requirements Definition document is the requirements definition document of a new SIS for a small college. The college offers both online and face-to-face, brick-and-mortar classes to its undergraduate student population. The goal of the SIS is to maintain and track the college’s information about its students, courses, and classes. The SIS is also used to automate the class registrations process. The SIS system should be accessible as a website and as a mobile app to both students and enrollment staff. You are hired as a consultant software architect to design the SIS functional model consisting of: 2  A use case diagram  A use case description for each use case in your model Analyze the SIS requirements and formalize them as use cases. You should have between four to six use cases. Generate a use case diagram showing the actors associated with each use case and structure your use cases using <>, <>, and generalization relationships. The use case diagram must be generated by a UML drawing tool. Links to UML drawing tools:  draw.io  Visio Using the provided use case description template, provide a description for each use case in your use case diagram. Your functional model should be complete and professional. Be sure to integrate your instructor’s feedback from the milestone opportunity and use the provided Final Project Part I Solution Submission Template document to format your submission. Specifically, the following critical elements must be addressed:  Creation: Analyze the SIS requirements and formalize them as use cases in a use case diagram, showing the actors associated with each use case. You should have between four to six use cases. Structure your use cases using <>, <>, and generalization relationships. Provide a description for each use case that is correct, complete, and valid for the SIS system.  Testing: Verify and validate your functional model against the requirements of the SIS system.  Approach Explanation: Explain your approach to creating your functional model and the design decisions you made to create it.  Self-Reflection: Discuss your experience creating your functional model and the lessons you learned from it. Specifically, draw connections between your experience and the object-oriented techniques and methods discussed in this course. Milestone Milestone One: Functional Model In Module Two, you will submit a draft of your functional model based on the Student Information System Requirements Definitions document for the requirements definitions document. This milestone will be graded with the Milestone One Rubric. Final Project Part I Submission: SIS Structural Model: CRC Cards, Class Diagrams, and Reflection 3 In Module Four, you will submit Part I of your final project. It should be a complete, polished artifact containing all of the critical elements of the final project. It should reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Part I Rubric. Final Project Part I Rubric Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information, review these instructions. Guidelines for Submission: Use the Final Project Part I Solution Submission document and follow the formatting directions therein when submitting your work. Your functional model should be complete and professional. Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value Functional Model: Creation Meets “Proficient” criteria and presents the model as a coherent package Creates an appropriate functional model that includes a use case diagram of four to six use cases structured via <>, <>, and generalization relationships and provides a correct, complete, and valid description for each Creates a functional model, but model does not meet the specifications laid out in the prompt, contains inaccuracies, or is inappropriate Does not create a functional model 24 Functional Model: Testing Meets “Proficient” criteria and verification and validation process is particularly detailed and well-documented Verifies that the functional model is correct, complete, and valid given the provided requirements of the project Verification and validation of functional model contain inaccuracies or omit key details with respect to the provided requirements of the project Does not verify that the functional model is correct, complete, and valid given the provided requirements of the project 24 Functional Model: Approach Explanation Meets “Proficient” criteria and explanation shows keen insight into software systems design methodology Explains the approach taken to creating the functional model and provides specific detail justifying all design decisions Explains the approach taken to creating the model, but explanation contains inaccuracies or fails to include specific detail justifying all design decisions Does not explain the approach taken to creating the model 24 4 Functional Model: Self-Reflection Meets “Proficient” criteria and reflection demonstrates nuanced understanding of object-oriented techniques and methods Reflects upon lessons learned by drawing specific connections between the experience developing the functional model and the techniques and methods discussed in the course Reflects upon lessons learned, but reflection is cursory or fails to sufficiently draw specific connections between the experience and the techniques and methods discussed in the course Does not reflect upon lessons learned during the experience 24 Articulation of Response Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy to read format Submission has no major errors related to citations, grammar, spelling, syntax, or organization Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas 4 Total 100%

 
"Looking for a Similar Assignment? Order now and Get 10% Discount! Use Code "Newclient"