Micro-Project Report (SEN) 2020
Micro-Project Report (SEN) 2020
Signature:
Enrollment Student Name Marks out Marks out of Total out
No. of 6 for 4 for of 10
performance individual
in group performance
activity
1701160174 Akshay
Bangar
1801160175 Atharv
Gharge
1801160185 Aneesh
Phaphale
1801160181 Gaurav
Rahate
A Micro-Project Report
Of
(Extreme Programming)
Submitted by
In partial fulfilment if the requirement for the diploma in
Information Technology Department
UNDER GUIDENCE OF
PROF. D.P. Sapkal
GOVERNMENT POLYTECHNIC
THANE
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION
(2019-20)
GOVERNMENT POLYTECHNIC THANE
CERTIFICATE
4. Literature Review:
1. https://airbrake.io/blog/sdlc/extreme-programming
2. http://www.extremeprogramming.org/
3. https://www.geeksforgeeks.org/software-engineering-extreme-
programming-xp/
5. Actual Description:
o Rapid feedback: Team members understand the given feedback and react
to it right away.
o Quality work: A team that works well, makes a valuable product and
feels proud of it.
Now it’s time to learn about practices that turn a software development
group into dream teams.
o On-site Customer:
According to XP, the end customer should fully participate in
development. The customer should be present all the time to answer team
questions, set priorities, and resolve disputes, if necessary.
o Pair Programming:
This practice requires two programmers to work jointly on the same code.
While the first developer focuses on writing, the other one reviews code,
suggests improvements, and fixes mistakes along the way. Such teamwork
results in high-quality software, faster knowledge sharing but takes 15 to
60 percent more time. In this regard, it’s more reasonable trying pair
programming for long-term projects.
o Code Refactoring:
To deliver business value with well-designed software in every short
iteration, XP teams also use refactoring. The goal of this technique is to
continuously improve code. Refactoring is about removing redundancy,
eliminating unnecessary functions, increasing code coherency, and at the
same time decoupling elements. Keep your code clean and simple, so you
can easily understand and modify it when required would be the advice of
any XP team member.
o Continuous Integration:
Developers always keep the system fully integrated. XP teams take iterative
development to another level because they commit code multiple times a
day, which is also called continuous delivery. XP practitioners understand
the importance of communication. Programmers discuss which parts of the
code can be re-used or shared. This way, they know exactly what
functionality they need to develop. The policy of shared code helps
eliminate integration problems. In addition, automated testing allows
developers to detect and fix errors early, before deployment.
o Small Releases:
This practice suggests releasing the first version quickly and further
developing the product by making small and incremental updates. Small
releases allow developers to frequently receive feedback, detect bugs early,
and monitor how the product works in production. One of the methods of
doing so is the continuous integration practice (CI) we mentioned before.
o Simple Design:
The best design for software is the simplest one that works. If any
complexity is found, it should be removed. The right design should pass all
tests, have no duplicate code, and contain the fewest possible methods and
classes. It should also clearly reflect the programmer’s intent.
o Coding Standards:
A team must have common sets of coding practices, using the same formats
and styles for code writing. Application of standards allows all team
members to read, share, and refactor code with ease, track who worked on
certain pieces of code, as well as make the learning faster for other
programmers. Code written according to the same rules encourages
collective ownership.
o System Metaphor:
System metaphor stands for a simple design that has a set of certain
qualities. First, a design and its structure must be understandable to new
people. They should be able to start working on it without spending too
much time examining specifications. Second, the naming of classes and
methods should be coherent. Developers should aim at naming an object as
if it already existed, which makes the overall system design understandable .
3. https://www.altexsoft.com/blog/business/ Google
extreme-programming-values-principles-
and-practices/website
9. Application of Micro-project:
Any software development company can use the method of
Extreme Programming while performing its projects. The only
thing they should do before working with XP is to understand its
main principles and theoretical basics.
Most of the researchers and developers agree that Extreme
Programming should be applied to systems that have no constant
functionality features. If the system should often change its
functions it requires the use of Extreme Programming method.
_________________ END_____________________
Actual Resources Used:
3. https://www.javatpoint.com/java- Google
tutorial
website
5. jdk 13.0.1
Deposit Amount:
Withdraw amount:
Display Account Details:
Skill Developed/Learning outcome of this Micro-
Project:
We got familiar with basic concepts of Online Banking System.
We got familiar with the concepts of Java Programming Language like
Inheritance, conditional loops while coding on software called jdk (Java
Development Kit) very clearly.
Skill developed of using various system built Java packages according to its
use in program.
Applications of Micro-Project:
End
__________________________________________________________
__________________