Here are the steps to view the idea generation steps:
1. Student navigates to the Imagination Portal home page.
2. Student clicks on the "Imagination Steps" link in the top menu bar.
3. Student views the steps on the displayed page.
Post-conditions: Idea generation steps are displayed.
Summary Inputs: Source: Summary Outputs: Destination:
- Imagination Portal home page - User's web browser
- "Imagination Steps" link
The student is able to view the idea generation steps by navigating from the home page to the dedicated steps page.
The document provides guidance on project start-up for new project managers. It discusses establishing roles and responsibilities, defining objectives and scope, identifying benefits and risks, developing a project plan and timeline, and obtaining necessary resources and support. Effective communication and collaboration with stakeholders is emphasized throughout the start-up process.
The document provides an agenda for a training session on agile basics. The summary is:
The training session will cover key topics such as defining agility, comparing traditional and agile approaches, explaining the origins of agile and the agile manifesto. It will help participants understand the agile mindset and recognize the difference between doing agile and being agile. The session will also explore challenges to enabling agility and techniques for continuous improvement.
The document provides guidance for students on developing and implementing successful sustainability projects at Carleton College. It outlines the nine steps to take, including getting feedback, developing a project plan, pitching the idea, building a team, and overcoming obstacles. The guide also gives examples of past successful student projects and advice from sustainability leaders on campus.
The document discusses database normalization. It provides examples of entity-relationship diagrams for various scenarios like a hospital, police case tracking, and employee-project relationships. It explains how to identify entities, attributes, and relationships. Primary keys are assigned and many-to-many relationships are resolved using linking tables. The goals of normalization are outlined as removing repeating groups of data and attributes not fully dependent on primary keys to satisfy first, second, and third normal form.
Entity Relationship Diagrams (ERDs) are used to model relationships between entities in a database. The document discusses ERD components like entities, relationships, cardinality, and attributes. It provides an example of an ERD for a company with departments, supervisors, employees, and projects. Key entities are identified and their relationships and attributes are represented in the example ERD diagrams.
The document provides information on entity relationship diagrams (ERDs), including the objectives, components, and steps to create an ERD. It defines key ERD concepts like entities, attributes, relationships, and cardinality. It describes the entity modeling process and discusses how to recognize entities, attributes, relationships, and cardinalities in a database. It outlines the general steps to create an ERD, including identifying entities, finding relationships between entities, drawing a rough ERD, defining primary keys, identifying attributes, mapping attributes to entities, and drawing a fully attributed ERD. Sample ERDs are provided to illustrate concepts like cardinality constraints.
The document provides details about an online charity management system project. It acknowledges the guidance received from professors. It includes an abstract that describes the system as facilitating online donations, gift selection, tax implications, and gift delivery. It discusses the system having three modules. It also includes a SWOT analysis, feasibility analysis covering technical, economic, operational, legal and schedule aspects, and overview of the software development life cycle and agile model being suitable. It shows data flow diagrams and class diagram for the system.
The document outlines a proposed website project for a virtual project leader. The project aims to [1] create a website documenting the process of developing a project to serve as a reference for others, [2] include forms, procedures and milestones to demonstrate a standard approach to projects, and [3] allow for updates and suggestions to track changes over time. The project scope is moderate, using a simple development tool, and will be worked on during the developer's free time with a proposed 3 month timeline.
The document provides guidance on project start-up for new project managers. It discusses establishing roles and responsibilities, defining objectives and scope, identifying benefits and risks, developing a project plan and timeline, and obtaining necessary resources and support. Effective communication and collaboration with stakeholders is emphasized throughout the start-up process.
The document provides an agenda for a training session on agile basics. The summary is:
The training session will cover key topics such as defining agility, comparing traditional and agile approaches, explaining the origins of agile and the agile manifesto. It will help participants understand the agile mindset and recognize the difference between doing agile and being agile. The session will also explore challenges to enabling agility and techniques for continuous improvement.
The document provides guidance for students on developing and implementing successful sustainability projects at Carleton College. It outlines the nine steps to take, including getting feedback, developing a project plan, pitching the idea, building a team, and overcoming obstacles. The guide also gives examples of past successful student projects and advice from sustainability leaders on campus.
The document discusses database normalization. It provides examples of entity-relationship diagrams for various scenarios like a hospital, police case tracking, and employee-project relationships. It explains how to identify entities, attributes, and relationships. Primary keys are assigned and many-to-many relationships are resolved using linking tables. The goals of normalization are outlined as removing repeating groups of data and attributes not fully dependent on primary keys to satisfy first, second, and third normal form.
Entity Relationship Diagrams (ERDs) are used to model relationships between entities in a database. The document discusses ERD components like entities, relationships, cardinality, and attributes. It provides an example of an ERD for a company with departments, supervisors, employees, and projects. Key entities are identified and their relationships and attributes are represented in the example ERD diagrams.
The document provides information on entity relationship diagrams (ERDs), including the objectives, components, and steps to create an ERD. It defines key ERD concepts like entities, attributes, relationships, and cardinality. It describes the entity modeling process and discusses how to recognize entities, attributes, relationships, and cardinalities in a database. It outlines the general steps to create an ERD, including identifying entities, finding relationships between entities, drawing a rough ERD, defining primary keys, identifying attributes, mapping attributes to entities, and drawing a fully attributed ERD. Sample ERDs are provided to illustrate concepts like cardinality constraints.
The document provides details about an online charity management system project. It acknowledges the guidance received from professors. It includes an abstract that describes the system as facilitating online donations, gift selection, tax implications, and gift delivery. It discusses the system having three modules. It also includes a SWOT analysis, feasibility analysis covering technical, economic, operational, legal and schedule aspects, and overview of the software development life cycle and agile model being suitable. It shows data flow diagrams and class diagram for the system.
The document outlines a proposed website project for a virtual project leader. The project aims to [1] create a website documenting the process of developing a project to serve as a reference for others, [2] include forms, procedures and milestones to demonstrate a standard approach to projects, and [3] allow for updates and suggestions to track changes over time. The project scope is moderate, using a simple development tool, and will be worked on during the developer's free time with a proposed 3 month timeline.
Software Project Management: Project InitiationMinhas Kamal
Software Project Management: ResearchColab- Project Initiation (Document-1)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Running Head MASTER PROJECT MASTER PROJECT2Topi.docxcowinhelen
Running Head MASTER PROJECT
MASTER PROJECT2
Topic: Lesson learned
Master project
Through this project, one is made aware that a large number of international students provide so many opportunities. One of such opportunity is developing the website tailored to suit their different needs since the information on the internet not adequate for everyone need. Even before starting to develop a website, it is good to define the problem properly then come up with a suitable solution. The second step is carrying out a feasibility study that entails; studying the benefit that the site will generate, the stakeholders are people that will directly or indirectly use the site. Other factors include maintainability, risk, economic value and reliability.
The basic design of a project has six phases that include planning initiation, Designing, Developing, testing and documenting, implementation and post-implementation. For the project to be successful, it as to meet the post-agreement or the expected outcome, that is time, quality, cost and scope. However, there is a likelihood of risks such as unexpected software abnormalities, overestimation of the project team’s ability, failure to meet the deadline and security threats. Such risks may be mitigated by first identifying those risks assessing them and then prioritizing in a case of more than one risk. The most concerned risk should be given priority to be treated after that it should be monitored and controlled. Apart from the risk associated with website development there, some of the errors that web developer fails to observe.
HTML Validation Errors- these are hidden errors, that cannot be seen but search engines can detect them. These errors are likely to hurt your search engine ranking or hinder potential visitors from seeing them. Broken links can be eradicated by the use of website checker to ensure that the pages lead to live web pages.
Running head: SDIS INFORMATIVE ONLINE RESOURCE CENTER
SDIS Informative Online Resource Center 74
Capstone Project
SDIS Informative Online Resource Center
By
Christopher Millard, Emery Bullock, Hau Le, Hector Roman, & Swetha Yarra
Professor Lu Zhang
10/24/2016
Version History
Version
#
Created
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0
Hau Le
09/06/2016
Project Team
09/07/2016
Milestone 1
1.1
Hau Le
09/20/2016
Project Team
09/21/2016
Milestone 1 & 2
1.2
Chris Millard
10/9/2016
Project Team
10/10/2016
Milestone 1, 2, & 3
1.3
Hau Le
10/23/2016
Project Team
10/24/2016
Milestone 1, 2, 3, & 4
Executive Summary
Life of an international student in America can be tough. An international student has to deal with different types of challenges such as financial, cultural, social, and academic. Living in a new country, trying to understand a new culture, and speaking a different language can be tough. Small tasks such as finding textbooks for classes, looking for a tutoring service ...
For the week 7 Final Project you will create a presentation (CO8) ShainaBoling829
For the week 7 Final Project you will create a presentation (CO8) that builds upon the week 2 Project Plan and the week 4 Location and Access (Source Organization worksheet) that effectively communicates the knowledge you have gained during COMM120.
Please consider the following:
· Presentation will include an introduction, body, conclusion, and properly formatted reference/work cited slide in the citation style of your degree program (APA, MLA, or Chicago).
· Clear evidence that the topic was researched and expanded upon the week 2 Project Plan (CO2 & 5).
· Presentation provides audience with information to increase their knowledge of the topic presented (CO1).
· Presentation engages the audience by using elements such as images, graphs, and charts. Appropriate citations must be included.
· Three (3) vetted credible sources. One (1) of the sources must be scholarly and from the library.
· Appropriate length 7-9 slides.
If you have multimedia skills and want to add creative content to your presentation, please do! Try to add any of the following enhancements and as you do, think about how it will impact your presentation and improve communication with the intended audience.
· Voice narration, closed captioning, script.
· Appropriate background music (must be cited on reference page).
· Creative use of slide animations and transitions.
After submitting your presentation, review your TurnItIn Originality Report. (Note: Review the individual flags, decide why that text is flagged, and make corrections as appropriate.). Please see the attached rubric for grading guidelines.
Note: The Week 7 Final Project is a presentation and be turned in as a PowerPoint, a Prezi, or a different type of presentation software. If you chose something other than PowerPoint, you have to do the following:
· Submit a link to the presentation such as for Prezi.
· Ensure that the faculty can open the presentation.
· turn in a document with the presentation material so it can go through Turnitin.
Source Evaluation Worksheet
Alesha January
American Military University
May 29, 2022
Part I: Topic
The topic concerns customer care in various organizations. The concept of the project involves the development of a DFJ customer care software that will help in ensuring that customers care is provided in the most satisfying way (Behera & Bala, 2021). The primary idea is to create an effective software that will ensure that customers in organizations interact with the management properly and give their feedback without difficulties (Lotz et al, 2018). This will help the organizations in solving disputes involving the customers with ease as well as ensure that the services delivered to the customers are of high quality (Gupta & Mittal, 2021).
Part II: Source Evaluation
Source 1.
Article Title: Cognitive chatbot for personalized contextual customer service: Behind the Scene and beyond the Hype.
Article Author: Rajat Kumar Behera & Pradip Kumar Bala
Retrieval Inf ...
Software Project Management: Project CharterMinhas Kamal
Software Project Management: ResearchColab- Project Charter (Document-1.1)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Pathways to Technology Transfer and Adoption: Achievements and ChallengesTao Xie
Dongmei Zhang and Tao Xie. Pathways to Technology Transfer and Adoption: Achievements and Challenges. In Proceedings of the 35th International Conference on Software Engineering (ICSE 2013), Software Engineering in Practice (SEIP), Mini-Tutorial, San Francisco, CA, May 2013. http://people.engr.ncsu.edu/txie/publications/icse13seip-techtransfer.pdf
Improve Your Library: Using the 5 Phases of Project Management (February 2017)ALATechSource
The document discusses improving a library using the 5 phases of project management. It begins by introducing the phases of project management and some common terminology. It then focuses on the planning phase, which has two parts - initiation and planning & design. Initiation involves assessing needs, resources, stakeholders and risks to create a project charter. Planning & design further develops the plan, including defining the scope, deliverables, work breakdown structure, budget, timeline and risks. The document provides examples and templates to help effectively plan a project from start to finish.
CloudWatch: Mapping priorities and future collaboration for your projectDavid Wallom
Presentation @ NetFutures2016 on how building effective relationships is essential through all parts of a project from formation to closure. The CloudWATCH Cloud Clustering tool allows quantitative analysis of the cloud ecosystem landscape and a project or activities position in it.
Mapping Priorities and Future Collaborations for you ProjectsDavid Wallom
Presentation on the outputs of cloud computing clustering and how the self help tool can give insight to where you sit in the cloud ecosystem and who else you should be talking to.
This document provides a summary of a thesis submitted by Justin M. Ha in partial fulfillment of the requirements for a Bachelor of Applied Science degree. The thesis defines a project management process model for an e-commerce solutions provider engaging in projects to create and launch new websites for clients. It begins with an introduction that provides background on e-commerce and project management. A literature review then covers electronic commerce, project management principles and methodologies, and system development life cycles. The document outlines Ha's research methodology and introduces the e-commerce solutions provider, Novator Systems Ltd. It then presents a new "Standard Web Site Creation Process" model tailored for Novator's project management needs. The conclusion reflects on the outcomes and limitations of the
The Future for Educational Resource Repositories in a Web 2.0 Worldlisbk
Slides for a talk on "The Future for Educational Resource Repositories in a Web 2.0 World" given by Brian Kelly, UKOLN at an Edspaces workshop held at the University of Southampton on 4 November 2009.
See http://www.ukoln.ac.uk/web-focus/events/workshops/edspace-2009/
The document discusses key elements to include in a project charter such as the project description, objectives, scope, assumptions, constraints, roles and responsibilities, stakeholders, steps, deliverables, and risks. It emphasizes that the charter is an agreement between the project manager and sponsor that defines the project goals, deliverables, schedule, and resources. It should provide a clear and shared understanding of the project for all involved parties.
Final Year Projects (Computer Science 2013) - Syed Ubaid Ali JafriSyed Ubaid Ali Jafri
Final year project ideas and Aims related to computer science students, Students can get an idea and make their final year project belongs to the industry requirement.
Software Project Management: Project SummaryMinhas Kamal
Software Project Management: ResearchColab- Project Summary (Document-13)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
How to Build More Prosocial Teams by Hadassah MativetskyQA or the Highway
The document discusses how to build more prosocial teams. It provides an overview of prosocial, which combines concepts from common pool resources and multilevel selection theory. Prosocial tools are presented to analyze a group's needs and design a behavior change project using techniques from contextual behavioral science. Examples are given of how agile principles and practices can support the core design principles identified by Ostrom for managing common resources, such as trust, cooperation, and inclusive decision making. The talk aims to help groups improve their internal functioning and interactions with other groups.
Agile Methodology For Software DevelopmentDiane Allen
Here are the key advantages and disadvantages of using an Agile Scrum methodology for software development projects:
Advantages:
- Iterative approach allows for frequent delivery of working software and ability to adapt to changes more easily.
- Self-organizing cross-functional teams are better able to respond to changing priorities and requirements.
- Daily stand-up meetings promote regular communication and status updates.
- Sprints provide a fixed timebox to focus effort and keep projects on track.
Disadvantages:
- Upfront planning is reduced which can impact scheduling and budgeting if not managed properly.
- Testing and documentation may be reduced as focus is on working software over documentation.
- Requires buy-in and
APM webinar held on 27 April 2021.
Presenters:
Naomi Brooks, Sebastian Williams, Martin Paver
Revolutions, it’s been remarked, never go backward. Nor do they advance at a constant rate. Just consider the radical transformation unleashed by data analytics.
By now, it’s clear the data revolution is changing businesses and industries in profound and unalterable ways.
We have a real opportunity, as project professionals, to harness the benefits of data to support the progress of our projects.
We can only do this if we fully understand and embrace the fundamental requirements of data. This session will look to explore the why of data, providing an initial insight into why you should embrace it’s role in current and future projects.
Links:
https://youtu.be/AxXengxxNcQ
https://www.apm.org.uk/news/why-data-matters-webinar/
Software Project Management: Business CaseMinhas Kamal
Software Project Management: ResearchColab- Business Case (Document-3)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
More Related Content
Similar to CIS 477 - Senior Project - Imagination Portal
Software Project Management: Project InitiationMinhas Kamal
Software Project Management: ResearchColab- Project Initiation (Document-1)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Running Head MASTER PROJECT MASTER PROJECT2Topi.docxcowinhelen
Running Head MASTER PROJECT
MASTER PROJECT2
Topic: Lesson learned
Master project
Through this project, one is made aware that a large number of international students provide so many opportunities. One of such opportunity is developing the website tailored to suit their different needs since the information on the internet not adequate for everyone need. Even before starting to develop a website, it is good to define the problem properly then come up with a suitable solution. The second step is carrying out a feasibility study that entails; studying the benefit that the site will generate, the stakeholders are people that will directly or indirectly use the site. Other factors include maintainability, risk, economic value and reliability.
The basic design of a project has six phases that include planning initiation, Designing, Developing, testing and documenting, implementation and post-implementation. For the project to be successful, it as to meet the post-agreement or the expected outcome, that is time, quality, cost and scope. However, there is a likelihood of risks such as unexpected software abnormalities, overestimation of the project team’s ability, failure to meet the deadline and security threats. Such risks may be mitigated by first identifying those risks assessing them and then prioritizing in a case of more than one risk. The most concerned risk should be given priority to be treated after that it should be monitored and controlled. Apart from the risk associated with website development there, some of the errors that web developer fails to observe.
HTML Validation Errors- these are hidden errors, that cannot be seen but search engines can detect them. These errors are likely to hurt your search engine ranking or hinder potential visitors from seeing them. Broken links can be eradicated by the use of website checker to ensure that the pages lead to live web pages.
Running head: SDIS INFORMATIVE ONLINE RESOURCE CENTER
SDIS Informative Online Resource Center 74
Capstone Project
SDIS Informative Online Resource Center
By
Christopher Millard, Emery Bullock, Hau Le, Hector Roman, & Swetha Yarra
Professor Lu Zhang
10/24/2016
Version History
Version
#
Created
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0
Hau Le
09/06/2016
Project Team
09/07/2016
Milestone 1
1.1
Hau Le
09/20/2016
Project Team
09/21/2016
Milestone 1 & 2
1.2
Chris Millard
10/9/2016
Project Team
10/10/2016
Milestone 1, 2, & 3
1.3
Hau Le
10/23/2016
Project Team
10/24/2016
Milestone 1, 2, 3, & 4
Executive Summary
Life of an international student in America can be tough. An international student has to deal with different types of challenges such as financial, cultural, social, and academic. Living in a new country, trying to understand a new culture, and speaking a different language can be tough. Small tasks such as finding textbooks for classes, looking for a tutoring service ...
For the week 7 Final Project you will create a presentation (CO8) ShainaBoling829
For the week 7 Final Project you will create a presentation (CO8) that builds upon the week 2 Project Plan and the week 4 Location and Access (Source Organization worksheet) that effectively communicates the knowledge you have gained during COMM120.
Please consider the following:
· Presentation will include an introduction, body, conclusion, and properly formatted reference/work cited slide in the citation style of your degree program (APA, MLA, or Chicago).
· Clear evidence that the topic was researched and expanded upon the week 2 Project Plan (CO2 & 5).
· Presentation provides audience with information to increase their knowledge of the topic presented (CO1).
· Presentation engages the audience by using elements such as images, graphs, and charts. Appropriate citations must be included.
· Three (3) vetted credible sources. One (1) of the sources must be scholarly and from the library.
· Appropriate length 7-9 slides.
If you have multimedia skills and want to add creative content to your presentation, please do! Try to add any of the following enhancements and as you do, think about how it will impact your presentation and improve communication with the intended audience.
· Voice narration, closed captioning, script.
· Appropriate background music (must be cited on reference page).
· Creative use of slide animations and transitions.
After submitting your presentation, review your TurnItIn Originality Report. (Note: Review the individual flags, decide why that text is flagged, and make corrections as appropriate.). Please see the attached rubric for grading guidelines.
Note: The Week 7 Final Project is a presentation and be turned in as a PowerPoint, a Prezi, or a different type of presentation software. If you chose something other than PowerPoint, you have to do the following:
· Submit a link to the presentation such as for Prezi.
· Ensure that the faculty can open the presentation.
· turn in a document with the presentation material so it can go through Turnitin.
Source Evaluation Worksheet
Alesha January
American Military University
May 29, 2022
Part I: Topic
The topic concerns customer care in various organizations. The concept of the project involves the development of a DFJ customer care software that will help in ensuring that customers care is provided in the most satisfying way (Behera & Bala, 2021). The primary idea is to create an effective software that will ensure that customers in organizations interact with the management properly and give their feedback without difficulties (Lotz et al, 2018). This will help the organizations in solving disputes involving the customers with ease as well as ensure that the services delivered to the customers are of high quality (Gupta & Mittal, 2021).
Part II: Source Evaluation
Source 1.
Article Title: Cognitive chatbot for personalized contextual customer service: Behind the Scene and beyond the Hype.
Article Author: Rajat Kumar Behera & Pradip Kumar Bala
Retrieval Inf ...
Software Project Management: Project CharterMinhas Kamal
Software Project Management: ResearchColab- Project Charter (Document-1.1)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Pathways to Technology Transfer and Adoption: Achievements and ChallengesTao Xie
Dongmei Zhang and Tao Xie. Pathways to Technology Transfer and Adoption: Achievements and Challenges. In Proceedings of the 35th International Conference on Software Engineering (ICSE 2013), Software Engineering in Practice (SEIP), Mini-Tutorial, San Francisco, CA, May 2013. http://people.engr.ncsu.edu/txie/publications/icse13seip-techtransfer.pdf
Improve Your Library: Using the 5 Phases of Project Management (February 2017)ALATechSource
The document discusses improving a library using the 5 phases of project management. It begins by introducing the phases of project management and some common terminology. It then focuses on the planning phase, which has two parts - initiation and planning & design. Initiation involves assessing needs, resources, stakeholders and risks to create a project charter. Planning & design further develops the plan, including defining the scope, deliverables, work breakdown structure, budget, timeline and risks. The document provides examples and templates to help effectively plan a project from start to finish.
CloudWatch: Mapping priorities and future collaboration for your projectDavid Wallom
Presentation @ NetFutures2016 on how building effective relationships is essential through all parts of a project from formation to closure. The CloudWATCH Cloud Clustering tool allows quantitative analysis of the cloud ecosystem landscape and a project or activities position in it.
Mapping Priorities and Future Collaborations for you ProjectsDavid Wallom
Presentation on the outputs of cloud computing clustering and how the self help tool can give insight to where you sit in the cloud ecosystem and who else you should be talking to.
This document provides a summary of a thesis submitted by Justin M. Ha in partial fulfillment of the requirements for a Bachelor of Applied Science degree. The thesis defines a project management process model for an e-commerce solutions provider engaging in projects to create and launch new websites for clients. It begins with an introduction that provides background on e-commerce and project management. A literature review then covers electronic commerce, project management principles and methodologies, and system development life cycles. The document outlines Ha's research methodology and introduces the e-commerce solutions provider, Novator Systems Ltd. It then presents a new "Standard Web Site Creation Process" model tailored for Novator's project management needs. The conclusion reflects on the outcomes and limitations of the
The Future for Educational Resource Repositories in a Web 2.0 Worldlisbk
Slides for a talk on "The Future for Educational Resource Repositories in a Web 2.0 World" given by Brian Kelly, UKOLN at an Edspaces workshop held at the University of Southampton on 4 November 2009.
See http://www.ukoln.ac.uk/web-focus/events/workshops/edspace-2009/
The document discusses key elements to include in a project charter such as the project description, objectives, scope, assumptions, constraints, roles and responsibilities, stakeholders, steps, deliverables, and risks. It emphasizes that the charter is an agreement between the project manager and sponsor that defines the project goals, deliverables, schedule, and resources. It should provide a clear and shared understanding of the project for all involved parties.
Final Year Projects (Computer Science 2013) - Syed Ubaid Ali JafriSyed Ubaid Ali Jafri
Final year project ideas and Aims related to computer science students, Students can get an idea and make their final year project belongs to the industry requirement.
Software Project Management: Project SummaryMinhas Kamal
Software Project Management: ResearchColab- Project Summary (Document-13)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
How to Build More Prosocial Teams by Hadassah MativetskyQA or the Highway
The document discusses how to build more prosocial teams. It provides an overview of prosocial, which combines concepts from common pool resources and multilevel selection theory. Prosocial tools are presented to analyze a group's needs and design a behavior change project using techniques from contextual behavioral science. Examples are given of how agile principles and practices can support the core design principles identified by Ostrom for managing common resources, such as trust, cooperation, and inclusive decision making. The talk aims to help groups improve their internal functioning and interactions with other groups.
Agile Methodology For Software DevelopmentDiane Allen
Here are the key advantages and disadvantages of using an Agile Scrum methodology for software development projects:
Advantages:
- Iterative approach allows for frequent delivery of working software and ability to adapt to changes more easily.
- Self-organizing cross-functional teams are better able to respond to changing priorities and requirements.
- Daily stand-up meetings promote regular communication and status updates.
- Sprints provide a fixed timebox to focus effort and keep projects on track.
Disadvantages:
- Upfront planning is reduced which can impact scheduling and budgeting if not managed properly.
- Testing and documentation may be reduced as focus is on working software over documentation.
- Requires buy-in and
APM webinar held on 27 April 2021.
Presenters:
Naomi Brooks, Sebastian Williams, Martin Paver
Revolutions, it’s been remarked, never go backward. Nor do they advance at a constant rate. Just consider the radical transformation unleashed by data analytics.
By now, it’s clear the data revolution is changing businesses and industries in profound and unalterable ways.
We have a real opportunity, as project professionals, to harness the benefits of data to support the progress of our projects.
We can only do this if we fully understand and embrace the fundamental requirements of data. This session will look to explore the why of data, providing an initial insight into why you should embrace it’s role in current and future projects.
Links:
https://youtu.be/AxXengxxNcQ
https://www.apm.org.uk/news/why-data-matters-webinar/
Software Project Management: Business CaseMinhas Kamal
Software Project Management: ResearchColab- Business Case (Document-3)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Similar to CIS 477 - Senior Project - Imagination Portal (20)
1. University of Southern Indiana
CIS 477
Fall 2015
Dr. Bačić
Project Documentation for:
Team:
Kyle Niemeier
Kurt Wasson
Geoffrey Beaven
Christopher Kimberlain
Lindsey Howes
Lindsey Witty
Wyatt Rondot
2.
3. Table of Contents
PART I: PLANNING..................................................................................................................5
SYSTEM REQUEST ............................................................................................................................ 6
FEASIBILITY ANALYSIS ....................................................................................................................... 7
PROJECTED BUDGET PLAN............................................................................................................... 10
PROJECT PLAN .............................................................................................................................. 11
PART II: ANALYSIS................................................................................................................13
SYSTEM REQUIREMENTS ................................................................................................................. 14
USE CASES.................................................................................................................................... 15
LOGICAL DFD ............................................................................................................................... 20
LOGICAL ERD................................................................................................................................ 21
PART III: DESIGN ..................................................................................................................23
ALTERNATIVE MATRIX .................................................................................................................... 24
ARCHITECTURE DESIGN................................................................................................................... 25
HARDWARE AND SOFTWARE SPECS .................................................................................................. 26
USE SCENARIOS............................................................................................................................. 27
INTERFACE DESIGN......................................................................................................................... 28
PROGRAM DESIGN......................................................................................................................... 31
PHYSICAL DFD.............................................................................................................................. 32
PHYSICAL ERD .............................................................................................................................. 33
DATA DICTIONARY ......................................................................................................................... 34
CRUD MATRIX ............................................................................................................................. 35
PART IV: IMPLEMENTATION.................................................................................................37
USER DOCUMENTATION ................................................................................................................. 38
PART V: TEAM INFORMATION..............................................................................................43
TEAM CONTRACT........................................................................................................................... 46
PROJECT CHARTER ......................................................................................................................... 47
TEAM PICTURES ............................................................................................................................ 48
TEAM RESUMES ............................................................................................................................ 51
6. Page 6 of 60
System Request
Business Need:
Provide USI with a web based portal to allow students and interested problem solvers the
resource to submit ideas, learn about the process of innovative problem solving, as well
as present “Sponsored Problems” that give incentives to solve.
Functionality:
This will be a sub-site the university can use to include on its main website. We will
provide the functionality and programming though HTML, CSS, JavaScript, as well as any
other resource we see beneficial; this could range from Microsoft Excel to MySQL.
Expected Value:
USI does not have this type of web portal currently on its website. There is no outlet or
database for students to express and host their ideas, solutions, or problems. This portal
will allow the USI community to get involved in innovation concerning multiple areas.
Potential ideas can lead to development in USI as well as the Evansville area. Business
ideas, solutions, as well as current problems can be expressed and given attention. The
idea of an innovation portal also transcends one specific community; this idea could grow
into a regional development. Government interties as well as other funding prospects
can be shown the innovation and creation happening at the University of Southern
Indiana.
Special Issues or Constraints:
This project has limited human resources as well as limited time. The project window is
projected to be 3 months; budget is also nonexistent. Dr. Khayum is open to ideas and
direction; the project itself is very open ended. Dr. Khayum wants this project to be the
foundation to a possible website that can be functional outside of USI.
7. Page 7 of 60
Feasibility Analysis
Project Summary:
Our client has requested an imagination portal in which users will go to a webpage and
submit ideas or solutions on a specific topic. Possible topics could include school, local,
and personal issues. In addition to idea submissions, we want users to also be able to
submit solutions for previous ideas as well. Because this tool may eventually be opened
up to a wider audience, scalability is going to be a very important factor in this project.
Economic Feasibility:
If we are to use USI’s resources, there should not be any costs in order to complete this
project. However, assuming we are unable to use the resources as expected, and
assuming this portal will go beyond the boundaries of USI, some costs may be incurred.
If we were to host our own web page, a business class web-hosting license with Arvixe
would cost approximately $22-35 a month. This service also provides a website builder
which would make development quite easy and efficient. However, due to the cost for
Arvixe to host our site, we are forced to turn to weebly.com where a free webpage hosting
option is offered with a few limitations that will not affect the outcome of the project.
If we can use the already existing USI database then there will not be any additional
database costs. However, if in the future the project goes beyond the USI domain, a
separate database would need to be implemented. MySQL Enterprise Edition would cost
approximately $5,000 and has many enterprise monitoring tools that would be included
with it.
Development Costs:
Project Length in Weeks: 16
Hours Per Week: 8
Team Members: 7
Expected Total Cost: $12,120
8. Page 8 of 60
Risk:
Because of the resources being used for the project being primarily free to use (Weebly
and the USI form submission), economic risk is low for the project. There is a low chance
of changes to the costs of the project over the development timeframe.
Overall:
Financially, this project will be very inexpensive to accomplish. There will be little to no
direct operating costs. Many of the tools that we need for the immediate project should
all be accessible through USI’s current infrastructure. Only when this application is scaled
to a higher level and begins to serve more users will a higher cost be necessary.
Organizational Feasibility:
Project Champion:
Our project champion is Dr. Mohammed Khayum, the Dean of the Romain College of
Business at the University of Southern Indiana. Dr. Khayum is the client for which meets
will be held and he will be able to shape the project throughout the SDLC.
Project Team:
Our project will require a structured deadline of tasks that will need to be completed by
each responsible project member. The members consist of three developers, one web
designer, one business analyst, one client liaison, and one documentation manager. Tasks
will be assigned and maintained in Microsoft Project throughout the course of the project.
Given the scope of this project we think that we have aligned the roles so that each team
member will be a critical asset to the overall success of the group and the project as a
whole.
Users:
The portal will be very attractive, modern, and easy to navigate. The process for
submitting a new idea/innovation will be very elaborate as well as thought-provoking.
This will help attract students who may have an innovative idea, to the portal. Word of
mouth and, hopefully, University advertising will be the primary ways to get the attention
of the student body, and after surveying friends and acquaintances of our project
members, a significant number of submissions are predicted.
9. Page 9 of 60
Risk:
There is moderate organizational risk when implementing any website or portal. Will
people want to use it? What will compel users to visit and submit ideas to the portal?
These questions will be addressed throughout the project. The appeal design and word-
of-mouth promotion of the website is hoped to mitigate some of this risk.
Technical Feasibility:
Our website will be created and managed using weebly.com as the domain provider as
well as the framework. Since it will only apply to students at the University, when a user
gets far enough into the idea submission process, our weebly page will automatically
redirect the user to another web page with a submission field from within the USI domain.
Using USI’s internal domain will make signing-on and navigating a simple and intuitive
process rather than using an outside service to do so. There will not be a need for user’s
to create new accounts/passwords to access the portal. All of this will be taken care of
by USI’s internal IT department. In addition, since our form webpage will be hosted
internally, all hardware limitations and future capacity limits will be determined by the
Information Technology department on campus. Our webpage will simply rely on
resources that are already present within the USI domain.
A database may need to be implemented in order to store ideas, solutions, categories,
and even future Evansville user accounts. If we are able to use a USI database as well this
would be provided at no additional cost to the project.
Risk:
Because the size of the team is quite small, risk is moderate. We don’t predict any
problems throughout developing the portal, but, as with all technical projects, something
can always change or negatively affect the direction of a project. Our technical
background due to attending the college of business is hoped to mitigate this risk.
14. Page 14 of 60
System Requirements
1. Functional Requirements
1.1 The System should have the capability for users to submit ideas and solutions
1.1.1 The system should step you through submissions
1.1.2 The system should provide content on how to develop ideas and
solutions
1.1.3 The system should give examples of former quality ideas and
solutions
1.1.4 The system should only accept submission from specific users
1.1.5 The system should have some way of recording submissions
1.2 The system should present the sponsored challenge
1.2.1 The system should give brief information on the sponsor
1.2.2 The system should explain what the sponsor is looing for
1.2.3 The system should explain the incentives the sponsor is giving for
submissions
1.3 The system should provide more information about the portal
1.3.1 The system should have an section explaining Dr. Khayum’s idea
1.3.2 The system should give information about the purpose of the website
1.3.3 The system should give information about the Portal Surfers
1.4 The system should be a showcase for the team for future resumes and jobs
1.4.1 The system should be efficient and designed well
1.4.2 The system should use implement practice development techniques
2. Nonfunctional Requirements
2.1 Culture
2.1.1 The system will be written in English
2.1.2 The system will be targeted at the USI community specifically
students
2.2 Other
2.2.1 The system will have aspects of USI throughout the website
2.2.2 The system will be targeted to college students
2.2.3 The system should stimulate student involvement with local
businesses and the Evansville community in general
2.3 Performance
2.3.1 The system should be efficient and intuitive to use
2.4 The system will be written in HTML with CSS and JavaScript
2.5 The system should meet the need for mobile use
15. Page 15 of 60
Use Cases
Use Case 1
Use Case Name: View Idea Submission
Page
UC ID: 1
Actor: Student Priority: Very High
Description: This step in the process allows a student to navigate to the idea submission page
Trigger: Student desires to view
idea submission web
page
Trigger Type: External
Preconditions: Student web browser open
Normal Course: Information for Steps:
1.) Student navigates to Imagination
Portal Home web page
2.) Student clicks on “Featured
Challenges” button
3.) Student clicks on “Featured
Challenges” banner
Imagination Portal URL
Alternative Course: Information for Steps:
1b.) Student backs out of website
2b.) Student clicks on a circle representing
another topic within “Categories”
3b.) Student navigates to page through
“Portal” within the menu button
Alternative Challenges
Post-conditions: Idea Submission Page is displayed
Summary Inputs: Source: Summary Outputs: Destination:
-Submission page -User web browser
16. Page 16 of 60
Use Case 2
Use Case Name: View Idea Generation
Steps
UC ID: 2
Actor: Student Priority: Very High
Description: This step in the process allows a student to navigate to and view the Idea
Generation Steps.
Trigger: Student desires to view
idea generation steps
Trigger Type: External
Preconditions: Student web browser open
Normal Course: Information for Steps:
1.) Student navigates to Imagination
Portal Home web page
2.) Student navigates to “Imagination
Steps” using menu button at top of
page
3.) Student navigates to the bottom of the
page and clicks button for next step
Imagination Portal URL
Alternative Course: Information for Steps:
1b.) Student backs out of website
Post-conditions: Idea generation video and other step information is displayed
Summary Inputs: Source: Summary Outputs: Destination:
-Idea generation
video and other
information
displayed
-User web browser
17. Page 17 of 60
Use Case 3
Use Case Name: Submit Idea UC ID: 3
Actor: Student Priority: Very High
Description: This step in the process allows a student to submit an idea through use of the
portal.
Trigger: Student desires to
submit idea
Trigger Type: External
Preconditions: Submission web page is open
Normal Course: Information for Steps:
1.) Student enters their Student ID
information into field on page
2.) Student clicks “login”
3.) Student enters their Idea for the
featured challenge
4.) Student submits the idea
USI Student ID
Student Idea Information
Alternative Course: Information for Steps:
1b.) Student backs out of submission page
Post-conditions: Student has submitted their idea to the database
Summary Inputs: Source: Summary Outputs: Destination:
-User idea
Information
-Student ID
-User web browser -Completion dialog
-Database entry
-User web browser
-Idea database
18. Page 18 of 60
Use Case 4
Use Case Name: View “FAQ” Web Page UC ID: 4
Actor: Student Priority: Very High
Description: This step in the process allows a student to see frequently asked questions about
the website or featured challenge.
Trigger: Student has questions
about the website or
challenge
Trigger Type: External
Preconditions: Student web browser open
Normal Course: Information for Steps:
1.) Student navigates to Imagination
Portal Home web page
2.) Student navigates to page through
“FAQ” within the menu button
Imagination Portal URL
Alternative Course: Information for Steps:
1b.) Student backs out of website
Post-conditions: Frequently asked questions about the website or featured challenge are displayed
Summary Inputs: Source: Summary Outputs: Destination:
-Frequently asked
questions
-User web browser
Use Case 5
19. Page 19 of 60
Use Case Name: View “About” Web Page UC ID: 5
Actor: Student Priority: Very High
Description: This step in the process allows a student to see who the creators of the site are and
where the idea for the website and its contents came from.
Trigger: Student desires
information on the origin
of the website
Trigger Type: External
Preconditions: Student web browser open
Normal Course: Information for Steps:
1.) Student navigates to Imagination
Portal Home web page
2.) Student navigates to page through
“About” within the menu button
Imagination Portal URL
Alternative Course: Information for Steps:
1b.) Student backs out of website
Post-conditions: Information on the creators and the origin of the website is displayed
Summary Inputs: Source: Summary Outputs: Destination:
-Information
about the website
-User Web Browser
24. Page 24 of 60
Alternative Matrix
An alternative matrix has been created to help determine the appropriate back-end for the
Imagination Portal. To determine the appropriate back-end we compared the original idea of
using USI's internal email service to a purchased MySQL database service. There are strong
positives and negatives for both services.
USI email, although would require manual intervention of all submitted ideas, would be free of
charge, is already developed, and will be supported by USI’s IT department. Because cost is a
huge factor in this project, the price along with the other benefits is superior to the database
method.
Although not immediately selected, the database method would be absolutely necessary when
this site begins to scale to a greater audience as expected in the future. There will be an initial
$5,000 flat cost with no additional cost for a business class license. After a database is
implemented it would allow for application integration to automatically store submissions on our
website and would be able to support a larger amount of user submissions.
Evaluation Criteria
Relative
Importance USI E-mail Score (1 - 5)
Weighted
Score MySQL Database Score (1 - 5)
Weighted
Score
Technical Issues:
Maintenance 10
IT Department
at USI 5 50
Will require
ongoing
maintenance
person 2 20
Development 20
Already
developed 5 100
Requires
creation 3 60
Economic Issues:
Cost 30 $0 5 150 $5,000 1 30
Organizational
Issues:
Ongoing support 20
IT Department
at USI 5 100
Will require
ongoing support
person 3 60
Features:
Feature 20
Manually
monitor each
submission 1 20
Allows for
application
integration to
automatically
store
submissions on
our website 5 100
Total 100 420 270
Back-end
26. Page 26 of 60
Hardware and Software Specs
For this project we will need a domain name and a server to host. We will also be using
an outside forms provider. The site will also have a dedicated email to hold the
submissions.
Web server Client Device
Domain name Internet browser
Forms submission Email for submission
Dedicated Email
27. Page 27 of 60
Use Scenarios
User Wishes to Contact Us or Current Sponsor
1. User will login using their USI credentials in order to submit
contact information
User Submits Content
1. User will login using their USI credentials in order to submit
ideas.
2. User will choose the category that best fits the idea they
wish to submit.
3. User presses submit and the idea is emailed to site
administrators for approval.
2. User fills out the appropriate contact information and it is
submitted to either the Imagination Portal Site Administrators
or it can be sent to the current site sponsor.
3. Imagination Portal Site Administrator or Sponsor reviews
contact information and responds as necessary.
Site Administrator Approves or Denies Content
1. Site Administrator receives an idea from the Imagination
Portal in the form of an email.
2. Site Administrator can choose to ignore and do nothing
with spam and/or offensive idea submissions.
3. If idea fits the websites goals and is categorized correctly,
the Site Administrator can choose to post the idea for all users
to see.
User visits Imagination Portal
1. User will click Imagination Portal link/icon on MyUSI
OR
2. User will type in Imagination Portal URL.
User Browses Site Content
1. User will be greeted with a home page that explains what
the site is about. There will also be a video and information
for sponsor challenges.
2. User will be able to click on various links to either submit
ideas, view previous best ideas, contact the site
administrator, and see sponsor information
34. Page 34 of 60
Data Dictionary
Module
Name
Field Name Data
Type
Data Description
Student STU_EMAIL
STU_SUBNUM
string
integer
Unique idea for email of student.
Student submission number.
Page PAGE_ID
PAGE_NAME
PAGE_DESC
integer
string
string
Unique identifier for page.
Name of the page.
Description of the page.
Form FORM_ID
FORM_NAME
ORG_TITLE
integer
string
string
Unique identifier for form.
Name of the form.
Title of the organization the form is for.
Host HOST_EMAIL
HOST_NAME
string
string
Unique identifier for email of host.
Name of host.
Client CLNT_ID
CLNT_NAME
CLNT_SINCE
integer
string
integer
Unique identifier for client.
Name of client.
Amount of time he/she has been a client.
35. Page 35 of 60
CRUD Matrix
The CRUD Matrix is used to determine who has access to certain portions of the website. In
addition, this matrix will also help determine the level of access that each user has.
C - Create
R - Read
U - Update
D - Delete
CRUD Matrix
User Administrator
Sponsor:
Sponsor Challenge Form CR CRUD
Contact:
Contact Us Form C CRUD
Client Contact Form C CRUD
Sponsor Contact C CRUD
Submissions:
Category for regular submissions CR CRUD
Submission Form CR CRUD
55. Page 55 of 60
Lindsey Howes
6304 N Blackburn Rd, Petersburg, IN 47567 | 812-789-6837 | LindseyJHowes@gmail.com
EDUCATION
BACHELOR OF SCIENCE | DECEMBER 2015 | UNIVERSITY OF SOUTHERN INDIANA, EVANSVILLE, IN
· Major: Computer Information Systems
· Emphasis: IS Management
SKILLS
· Database Design
· Experienced in SQL
· Website and portal monitoring
· Proficient in Microsoft Office
· C# programming knowledge
· Write clearly and concisely
· Organized
· Meet deadlines
· Excellent communication skills
· Work well with others
· Problem-solving skills
· Java experience
EXPERIENCE
INTERN IN ANALYTICS | METRONET, EVANSVILLE, IN | NOVMEBER 2015 TO CURRENT
· Work on analytics projects as instructed by the analytics manager.
· Use Google Earth in daily projects.
· Assist in finding areas to install fiber optic cables.
BASKETBALL INSTRUCTOR | YMCA, EVANSVILLE, IN | SEPTEMBER 2015 TO CURRENT
· Assist the Head Instructor with instructing basketball players in the rules, regulations, equipment, and techniques.
· Organize and direct individual and small practice activities/exercises.
· Assist the Head Instructor with supervising athletes during practices and competition.
SALES ASSOCIATE | SWEET-D-LICIOUS KETTLE KORN, LLC, WINSLOW, IN | AUGUST 2014 TO CURRENT
· Ensure high levels of customer satisfaction through excellent sales service.
· Remain knowledgeable of products offered and discuss available options.
· Assess customers’ needs and provides assistance and information on products.
· Travel to widen customer base.
VOLUNTEER COMPUTER & PROMOTIONAL ACTIVITIES
· ASSOCIATION OF INFORMATION TECHNOLOGY PROFESSIONALS, USI CHAPTER
· August 2014 to Current
· Competed in the 2015 AITP National Conference for USI: Security, database, and Microsoft Office competitions.
· USI SPRINGFEST COMMITTEE
· September 2013 to May 2014
· Helped upkeep website/Facebook/Twitter.
· EVANSVILLE ICEMEN ICICLES PROMOTIONAL TEAM
· September 2013 to June 2014
58. Page 58 of 60
Wyatt Rondot
8140 B O’Daniel South
Evansville, IN 47712
317-503-2073
wrondot@gmail.com
Objective
To obtain a position that will enable me to utilize my strong communication skills,
technological background, and ability to work effectively alone or as part of a group.
Education
Bachelor of Science Degree in Computer Information Science
August 2012- Expected Graduate May 2016
University of Southern Indiana
Evansville, IN
AACSB Accredited Romain College of Business
Work Experience
IT Paid Internship April 2014 - Present
Solve faculty email and web-page problems
Screen phone calls for IT Department
Learn to translate English-based problems into computer solutions
Volunteer Service
Senior Community Project Sep 2011 - Jan 2012
Technology Recycle Day - Organized community recycling drive which collected
7000 pounds of electronics for recycling
Extracurricular Activities
Boy Scouts Feb 2000 - Jul 2011
Order of the Arrow - Star Boy Scout Rank - Patrol Leader - Quartermaster -
Historian – Fire Crafter - Monthly and Annual Service Projects
Keywords
SDLC, Data Analytics, Business Strategies, Effective, Efficient, Leadership,
Communication, Group-Think, Big Data, Decision support, Application Driven,
Data warehouse, Agile programing, Computer software solutions, Powerful